From: Mel Gorman <mel@csn.ul.ie>
To: Andi Kleen <ak@suse.de>
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:25:33 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606071718380.31410@skynet.skynet.ie> (raw)
In-Reply-To: <200606071720.22242.ak@suse.de>
On Wed, 7 Jun 2006, Andi Kleen wrote:
>
>> 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.
>
ok, that's true. The watermarks would be higher if memmap and the kernel
image is not taken into account. Arguably, the same applies to bootmem
allocations. This hits all architectures *except* x86_64.
> Especially for the 16MB DMA zone it can make a difference if you
> account 4MB kernel in there or not.
>
I'm guessing it's a difficult-to-trigger problem or it would have been
reported for other arches. Assuming it can be triggered and that is what
was causing your problems, it's still worth fixing in the arch-independent
code rather than burying it in arch/somewhere, right?
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2006-06-07 16:25 UTC|newest]
Thread overview: 15+ 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 ` [PATCH 1/5] Introduce mechanism for registering active regions of memory 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:48 ` [PATCH 3/5] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-06-06 13:48 ` [PATCH 4/5] Have x86_64 " Mel Gorman
2006-06-06 13:48 ` [PATCH 5/5] Have ia64 " Mel Gorman
2006-06-06 23:43 ` [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Andrew Morton
2006-06-07 9:42 ` Mel Gorman
2006-06-07 9:45 ` Andi Kleen
2006-06-07 10:11 ` Mel Gorman
2006-06-07 10:16 ` Andi Kleen
2006-06-07 10:54 ` Mel Gorman
2006-06-07 15:20 ` Andi Kleen
2006-06-07 16:25 ` Mel Gorman [this message]
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=Pine.LNX.4.64.0606071718380.31410@skynet.skynet.ie \
--to=mel@csn.ul.ie \
--cc=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=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 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).