This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/15390] Add /proc/meminfo data to memory.stp tapset
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 23 Apr 2013 14:56:39 +0000
- Subject: [Bug tapsets/15390] Add /proc/meminfo data to memory.stp tapset
- Auto-submitted: auto-generated
- References: <bug-15390-6586 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15390
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #1 from David Smith <dsmith at redhat dot com> 2013-04-23 14:56:39 UTC ---
This is an interesting idea, that seems doable. You are right, the kernel
internal interface has changed somewhat over time (from looking at 2.6.9 source
vs. current source). For the example you included, I wonder if it wouldn't be
better to go ahead and call si_meminfo(), which would insulate us from kernel
changes a bit.
Which of the /proc/meminfo values would you consider most helpful for stap to
provide?
Another thought I had here was we could to name the stap functions after the
associated /proc/meminfo output, i.e. meminfo_memtotal(), meminfo_memfree(),
meminfo_buffers(), etc.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.