From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Adam Litke <agl@us.ibm.com>,
linux-mm@kvack.org, ak@suse.de, linux-kernel@vger.kernel.org,
kenneth.w.chen@intel.com
Subject: Re: [RFC] NUMA memory policy support for HUGE pages
Date: Fri, 11 Nov 2005 13:23:51 -0800 [thread overview]
Message-ID: <20051111212351.GT29402@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0511111051080.20589@schroedinger.engr.sgi.com>
On Fri, Nov 11, 2005 at 10:56:50AM -0800, Christoph Lameter wrote:
> Well since we got through respecting cpusets and allocating a page nearer
> to the processors so easy lets go for the full thing. Here is a draft of
> a patch that implements full NUMA policy support for it on top of the
> cpusets and the NUMA near allocation patch.
> I am not sure that this is the right way to do it. Maybe we better put the
> whole allocator into the policy layer like alloc_pages_vma?
> I needed to add two parameters to alloc_huge_page in order to get the
> allocation right for all policy cases. This means that find_lock_page
> has a plethora of parameters now. Maybe idx and the mapping could be
> deduced from addr and vma?
I've been awash in good hugetlb patches lately, and here's another one.
I don't have any strong feelings about this (apart from the code quality
observation), so could someone who has an interest in mempolicy affairs
(Andi, Adam, et al) chime in and say this is the way people want to go?
-- wli
--
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>
prev parent reply other threads:[~2005-11-11 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 18:56 Christoph Lameter
2005-11-11 20:28 ` Christoph Lameter
2005-11-14 15:06 ` Adam Litke
2005-11-14 18:09 ` Christoph Lameter
2005-11-14 21:46 ` Christoph Lameter
2005-11-14 22:30 ` Adam Litke
2005-11-14 23:25 ` Christoph Lameter
2005-11-15 12:18 ` William Lee Irwin III
2005-11-11 21:23 ` William Lee Irwin III [this message]
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=20051111212351.GT29402@holomorphy.com \
--to=wli@holomorphy.com \
--cc=agl@us.ibm.com \
--cc=ak@suse.de \
--cc=clameter@engr.sgi.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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