From: Zou Min <zoum@comp.nus.edu.sg>
To: Linux MM <linux-mm@kvack.org>
Subject: VM reference trace
Date: Tue, 18 Jun 2002 12:15:47 +0800 [thread overview]
Message-ID: <20020618121547.A15008@comp.nus.edu.sg> (raw)
Hi,
I am working on a problem which requires to get D: the number of distinct
pages (from user files or dynamically allocated or used by the kernel, ...)
used by the kernel+user processes in a workload.
One way I thought of is to firstly generate a reference trace, i.e. a sequence
of virtual memory addresses accessed by the workload, and then count the
the number of distinct addresses in the trace. (assuming the addresses are
page addresses).
In fact, I have found a library to do that, but it can only trace single
process in userland. And I have to modify, re-compile and re-link the program
which I want to trace. That's a bit tedious.
So, I want to ask if there are any better utilities to generate the trace,
or any way to get the number D directly.
Thanks in advance!
--
regards,
ZM
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
reply other threads:[~2002-06-18 4:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020618121547.A15008@comp.nus.edu.sg \
--to=zoum@comp.nus.edu.sg \
--cc=linux-mm@kvack.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