From: Anton Blanchard <anton@samba.org>
To: Andi Kleen <ak@suse.de>
Cc: manfred@colorfullife.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use numa policy API for boot time policy
Date: Thu, 10 Jun 2004 01:44:29 +1000 [thread overview]
Message-ID: <20040609154429.GA6152@krispykreme> (raw)
In-Reply-To: <20040605122239.4a73f5e8.ak@suse.de>
> It would be a one liner change to allow process policy interleaving
> for orders > 0 in mempolicy. But I'm not sure how useful it is, since
> the granuality would be really bad.
OK. Id like to take a quick look at order > 0 allocations during boot
to see if its worth it. The ppc64 page size is small and we might be
doing a significant number of order 1 allocations.
> Have you ever tried to switch to implement a vmalloc_interleave() for these
> tables instead? My bet is that it will perform better.
Im warming to this idea. We would need a per arch override, since there
is a trade off here between interleaving and TLB usage.
We also have a problem in 2.6 on our bigger machines where our dcache
hash and inode hash cache are limited to MAX_ORDER (16MB on ppc64). By
using vmalloc would allow us to interleave the memory and allocate more
than 16MB for those hashes.
Anton
next prev parent reply other threads:[~2004-06-09 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 1:43 [PATCH] Use numa policy API for boot time policy Andi Kleen
2004-06-05 1:56 ` Manfred Spraul
2004-06-05 2:18 ` Andi Kleen
2004-06-05 2:32 ` Anton Blanchard
2004-06-05 10:22 ` Andi Kleen
2004-06-05 10:48 ` Andi Kleen
2004-06-09 15:44 ` Anton Blanchard [this message]
2004-06-09 15:56 ` Andi Kleen
2004-06-09 16:12 ` Anton Blanchard
2004-06-05 10:20 ` Manfred Spraul
2004-06-05 10:33 ` Andi Kleen
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=20040609154429.GA6152@krispykreme \
--to=anton@samba.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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.