From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: <jrs@us.ibm.com>
Cc: <systemtap@sourceware.org>
Subject: RE: [SCRIPT] NUMA page fault accounting.
Date: Tue, 21 Mar 2006 18:58:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06B94913@scsmsx403.amr.corp.intel.com> (raw)
Jose R. Santos wrote:
> page_faults [pid(), $write_access ? 1 : 0] ++
> node_faults [pid(), addr_to_node($address)] ++
You could improve scalability of this script by using statistics to
maintain your count, e.g.:
page_faults [pid(), $write_access ? 1 : 0] <<< 1
node_faults [pid(), addr_to_node($address)] <<< 1
And then access the values with @count(page_faults[...]).
Other than that, this looks good. It might be nice to start publishing
case studies on the website, so if you have a real problem that you
solved with this, please share!
Josh
next reply other threads:[~2006-03-21 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 18:58 Stone, Joshua I [this message]
2006-03-21 20:37 ` Jose R. Santos
2006-03-22 15:57 ` Jose R. Santos
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 16:44 Jose R. Santos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CBDB88BFD06F7F408399DBCF8776B3DC06B94913@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=jrs@us.ibm.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).