All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@osdl.org>,
	davej@codemonkey.org.uk, tony.luck@intel.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, bob.picco@hp.com,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7
Date: Wed, 7 Jun 2006 17:20:22 +0200	[thread overview]
Message-ID: <200606071720.22242.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606071118230.20653@skynet.skynet.ie>


> Ok, while true, I'm not sure how it affects performance. The only "real" 
> value affected by present_pages is the number of patches that are 
> allocated in batches to the per-cpu allocator.

It affects the low/high water marks in the VM zone balancer.

Especially for the 16MB DMA zone it can make a difference if you
account 4MB kernel in there or not.

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@osdl.org>,
	davej@codemonkey.org.uk, tony.luck@intel.com, bob.picco@hp.com,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7
Date: Wed, 7 Jun 2006 17:20:22 +0200	[thread overview]
Message-ID: <200606071720.22242.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606071118230.20653@skynet.skynet.ie>


> Ok, while true, I'm not sure how it affects performance. The only "real" 
> value affected by present_pages is the number of patches that are 
> allocated in batches to the per-cpu allocator.

It affects the low/high water marks in the VM zone balancer.

Especially for the 16MB DMA zone it can make a difference if you
account 4MB kernel in there or not.

-Andi


WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@osdl.org>,
	davej@codemonkey.org.uk, tony.luck@intel.com, bob.picco@hp.com,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7
Date: Wed, 7 Jun 2006 17:20:22 +0200	[thread overview]
Message-ID: <200606071720.22242.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606071118230.20653@skynet.skynet.ie>

> Ok, while true, I'm not sure how it affects performance. The only "real" 
> value affected by present_pages is the number of patches that are 
> allocated in batches to the per-cpu allocator.

It affects the low/high water marks in the VM zone balancer.

Especially for the 16MB DMA zone it can make a difference if you
account 4MB kernel in there or not.

-Andi

--
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:[~2006-06-07 15:20 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 13:47 [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Mel Gorman
2006-06-06 13:47 ` Mel Gorman
2006-06-06 13:47 ` Mel Gorman
2006-06-06 13:47 ` [PATCH 1/5] Introduce mechanism for registering active regions of memory Mel Gorman
2006-06-06 13:47   ` Mel Gorman
2006-06-06 13:47   ` Mel Gorman
2006-06-06 13:47 ` [PATCH 2/5] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-06-06 13:47   ` Mel Gorman
2006-06-06 13:47   ` Mel Gorman
2006-06-06 13:48 ` [PATCH 3/5] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 13:48 ` [PATCH 4/5] Have x86_64 " Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 13:48 ` [PATCH 5/5] Have ia64 " Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 13:48   ` Mel Gorman
2006-06-06 22:59   ` (ProteanThread)
2006-06-06 22:59     ` (ProteanThread)
2006-06-06 23:43 ` [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Andrew Morton
2006-06-06 23:43   ` Andrew Morton
2006-06-06 23:43   ` Andrew Morton
2006-06-07  9:42   ` Mel Gorman
2006-06-07  9:42     ` Mel Gorman
2006-06-07  9:42     ` Mel Gorman
2006-06-07  9:45     ` Andi Kleen
2006-06-07  9:45       ` Andi Kleen
2006-06-07  9:45       ` Andi Kleen
2006-06-07 10:11       ` Mel Gorman
2006-06-07 10:11         ` Mel Gorman
2006-06-07 10:11         ` Mel Gorman
2006-06-07 10:16         ` Andi Kleen
2006-06-07 10:16           ` Andi Kleen
2006-06-07 10:16           ` Andi Kleen
2006-06-07 10:54           ` Mel Gorman
2006-06-07 10:54             ` Mel Gorman
2006-06-07 10:54             ` Mel Gorman
2006-06-07 15:20             ` Andi Kleen [this message]
2006-06-07 15:20               ` Andi Kleen
2006-06-07 15:20               ` Andi Kleen
2006-06-07 16:25               ` Mel Gorman
2006-06-07 16:25                 ` Mel Gorman
2006-06-07 16:25                 ` Mel Gorman
2006-06-09 12:57               ` Mel Gorman
2006-06-09 12:57                 ` Mel Gorman
2006-06-09 12:57                 ` 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=200606071720.22242.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bob.picco@hp.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mel@csn.ul.ie \
    --cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.