From: Mel Gorman <mgorman@suse.de>
To: Pintu Agarwal <pintu_agarwal@yahoo.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MMTests 0.01
Date: Fri, 5 Aug 2011 09:01:33 +0100 [thread overview]
Message-ID: <20110805080133.GS19099@suse.de> (raw)
In-Reply-To: <1312526302.37390.YahooMailNeo@web162009.mail.bf1.yahoo.com>
On Thu, Aug 04, 2011 at 11:38:22PM -0700, Pintu Agarwal wrote:
> Dear Mel Gorman,
>
> Thank you very much for this MMTest.
> It will be very helpful for me for all my needs.
> I was looking forward for these kind of mm test utilities.
>
> Just wanted to know, if any of these utilities also covers
> anti-fragmentation represent of the various page state in the form
> of jpeg image?
No, that particular script was not included as it needs a kernel patch
to be really useful and depends on parts of VM Regress that were very
ugly. As I've said before, I generally use unusable free space index
and fragmentation index if I'm trying to graph fragmentation-related
information. To record it, I use the "extfrag" monitor in monitors/
. It uses other helpers of which fraganalysis/show-buddyinfo is the
most important as it is the one that can read either /proc/buddyinfo
or use /proc/kpagefrags to build a more accurate picture.
--
Mel Gorman
SUSE Labs
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-05 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 14:38 MMTests 0.01 Mel Gorman
2011-08-05 6:38 ` Pintu Agarwal
2011-08-05 8:01 ` Mel Gorman [this message]
2011-08-11 5:25 ` Pintu Agarwal
2011-08-11 8:25 ` Mel Gorman
2011-08-10 23:50 ` Minchan Kim
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=20110805080133.GS19099@suse.de \
--to=mgorman@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pintu_agarwal@yahoo.com \
/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 NNTP newsgroup(s).