linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 2/8] Print out statistics in relation to fragmentation avoidance to /proc/fragavoidance
Date: Tue, 15 May 2007 20:23:21 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705152020140.12851@skynet.skynet.ie> (raw)
In-Reply-To: <Pine.LNX.4.64.0705151122110.31972@schroedinger.engr.sgi.com>

On Tue, 15 May 2007, Christoph Lameter wrote:

> On Tue, 15 May 2007, Mel Gorman wrote:
>
>>
>> This patch provides fragmentation avoidance statistics via
>> /proc/fragavoidance. The information is collected only on request so there
>
> The name is probably a bit strange.
>
> /proc/pagetypeinfo or so?
>

/proc/mobilityinfo ?

>> The first part is a more detailed version of /proc/buddyinfo and looks like
>>
>> Free pages count per migrate type
> If you have a header ^^^ then maybe add order on top of the numbers?

I can do that.

>> Node 0, zone      DMA, type    Unmovable      0      0      0      0      0      0      0      0      0      0      0
>> Node 0, zone      DMA, type  Reclaimable      1      0      0      0      0      0      0      0      0      0      0
>> Node 0, zone      DMA, type      Movable      0      0      0      0      0      0      0      0      0      0      0
>> Node 0, zone      DMA, type      Reserve      0      4      4      0      0      0      0      1      0      1      0
>> Node 0, zone   Normal, type    Unmovable    111      8      4      4      2      3      1      0      0      0      0
>> Node 0, zone   Normal, type  Reclaimable    293     89      8      0      0      0      0      0      0      0      0
>> Node 0, zone   Normal, type      Movable      1      6     13      9      7      6      3      0      0      0      0
>> Node 0, zone   Normal, type      Reserve      0      0      0      0      0      0      0      0      0      0      4
>>
>> The second part looks like
>>
>> Number of blocks type     Unmovable  Reclaimable      Movable      Reserve
>> Node 0, zone      DMA            0            1            2            1
>> Node 0, zone   Normal            3           17           94            4
>
> What is "blocks"? maxorder blocks? how do I figure out the blocksize?
> Could you include the blocksize here?
>

Each block contains nr_pages_pageblock number of pages. The number of 
pages can be determined from the dmesg output like;

Built 1 zonelists, mobility grouping on order 10.

In that case, nr_pages_pageblock would be (1UL << 10).

However, the information can be printed here as well as whether mobility 
is on or not.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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>

  reply	other threads:[~2007-05-15 19:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 15:03 [PATCH 0/8] Review-based updates to grouping pages by mobility Mel Gorman
2007-05-15 15:03 ` [PATCH 1/8] Do not depend on MAX_ORDER when " Mel Gorman
2007-05-15 18:19   ` Christoph Lameter
2007-05-15 19:19     ` Mel Gorman
2007-05-15 15:03 ` [PATCH 2/8] Print out statistics in relation to fragmentation avoidance to /proc/fragavoidance Mel Gorman
2007-05-15 18:25   ` Christoph Lameter
2007-05-15 19:23     ` Mel Gorman [this message]
2007-05-16  0:27       ` KAMEZAWA Hiroyuki
2007-05-15 15:04 ` [PATCH 3/8] Print out PAGE_OWNER statistics in relation to fragmentation avoidance Mel Gorman
2007-05-15 15:04 ` [PATCH 4/8] Mark bio_alloc() allocations correctly Mel Gorman
2007-05-15 15:04 ` [PATCH 5/8] Do not annotate shmem allocations explicitly Mel Gorman
2007-05-15 15:05 ` [PATCH 6/8] Add __GFP_TEMPORARY to identify allocations that are short-lived Mel Gorman
2007-05-15 18:29   ` Christoph Lameter
2007-05-16  0:36   ` KAMEZAWA Hiroyuki
2007-05-16  0:52     ` Christoph Lameter
2007-05-16  9:04       ` Mel Gorman
2007-05-15 15:05 ` [PATCH 7/8] Rename GFP_HIGH_MOVABLE to GFP_HIGHUSER_MOVABLE Mel Gorman
2007-05-15 18:29   ` Christoph Lameter
2007-05-15 15:05 ` [PATCH 8/8] Mark page cache pages as __GFP_PAGECACHE instead of __GFP_MOVABLE Mel Gorman
2007-05-15 18:31   ` Christoph Lameter
2007-05-15 19:52     ` Mel Gorman
2007-05-15 20:04       ` Christoph Lameter
2007-05-15 20:20         ` Mel Gorman
2007-05-15 20:36           ` Christoph Lameter
2007-05-15 20:50             ` Mel Gorman
2007-05-16  2:33 ` [PATCH 0/8] Review-based updates to grouping pages by mobility KAMEZAWA Hiroyuki
2007-05-16  8:58   ` Mel Gorman

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=Pine.LNX.4.64.0705152020140.12851@skynet.skynet.ie \
    --to=mel@csn.ul.ie \
    --cc=clameter@sgi.com \
    --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