From: "Peter Teoh" <htmldeveloper@gmail.com>
To: Kernel Newbies <kernelnewbies@nl.linux.org>, linux-mm@kvack.org
Subject: RFC: swaptrace tool
Date: Tue, 1 Apr 2008 16:54:46 +0800 [thread overview]
Message-ID: <804dabb00804010154t1aec08b3y3add0117fd409748@mail.gmail.com> (raw)
Go through this:
http://linux-mm.org/LinuxMMProjects
and u find there is no swaptrace. What I want is a visualization of
how the swap is being use. So once the operation is started, all
swap operation will be immediately written to an area in memory,
showing how the swap is written - the destination begin offset /
destination end offset/size info, and by what process/task - and its
correspond source begin offset, and source end offset. The data
content itself will not be recorded. Then after some time, via
ioctl() control, it will be stopped, and all that have been written to
memory will be flushed out to a file. This flushing to external file
only take place after the data collection has stopped, otherwise, the
swap operations itself will affect the behavior of the swap, thus
rendering the data collection invalid.
The purpose of this trace is to see/oberver how the swap is being
used, whether any algor can help to cluster the swap together so as to
enhance swap batch processing etc.
Any comment on this idea? Will it be useful?
--
Regards,
Peter Teoh
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-04-01 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 8:54 Peter Teoh [this message]
2008-04-01 9:31 ` Peter Chubb
2008-04-01 10:26 ` Mulyadi Santosa
2008-04-01 12:27 ` KOSAKI Motohiro
2008-04-02 1:23 ` Mulyadi Santosa
2008-04-02 2:58 ` KOSAKI Motohiro
2008-04-02 3:28 ` Peter Teoh
[not found] ` <47F301E2.6060403@gmail.com>
2008-04-02 5:52 ` Mulyadi Santosa
[not found] ` <f284c33d0804012249vb16325fpb9946487140c5905@mail.gmail.com>
2008-04-02 7:52 ` Peter Teoh
2008-04-02 7:55 ` KOSAKI Motohiro
2008-04-02 8:50 ` Peter Teoh
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=804dabb00804010154t1aec08b3y3add0117fd409748@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--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