linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	torvalds@osdl.org, akpm@osdl.org, kiran@scalex86.org,
	linux-mm@kvack.org
Subject: Re: [PATCH for 2.6.16] Handle holes in node mask in node fallback list initialization
Date: Thu, 16 Feb 2006 18:46:00 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602161828090.27424@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200602170310.19731.ak@suse.de>

On Fri, 17 Feb 2006, Andi Kleen wrote:

> No, in theory not, but changing that would require considerable changes 
> in the NUMA discovery code and I'm not planning to do that for 2.6.16 now.

Are you sure that the kernel can handle nodelists with holes everywhere? 
This is essentially a new feature requiring a review of all uses of 
node ranges.... I'd rather suggest to fix the arch.

> Also I think the generic code ought to handle that anyways. Why should
> we have node bitmaps if they can't have holes?

There are special cases for example in the slab allocator and possibly 
elsewhere too. F.e. have a look at __alloc_percpu which must allocate 
memory for cpus on offline nodes. These will then never be used. So 
hopefully not an issue just a waste of memory. There is more in 
alloc_alien_cache(). That is just the stuff that I know about off hand. 

> > ia64 has a lookup table. 
> x86-64 too.

So this is fixable in arch specific code.

--
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-02-17  2:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17  1:23 Andi Kleen
2006-02-17  1:40 ` Christoph Lameter
2006-02-17  1:46   ` Andi Kleen
2006-02-17  2:12     ` KAMEZAWA Hiroyuki
2006-02-17  1:51 ` Christoph Lameter
2006-02-17  2:10   ` Andi Kleen
2006-02-17  2:46     ` Christoph Lameter [this message]
2006-02-17  6:10   ` Yasunori Goto
2006-02-17  9:58     ` Andi Kleen
2006-02-17 11:23       ` Bob Picco
2006-02-17 12:15         ` Andi Kleen
2006-02-17 14:34           ` Lee Schermerhorn
2006-02-17 16:05     ` Christoph Lameter
2006-02-17  3:33 ` Yasunori Goto
2006-02-17 16:52 ` Linus Torvalds
2006-02-17 18:07   ` Andi Kleen
2006-02-17 18:38     ` Linus Torvalds

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.0602161828090.27424@schroedinger.engr.sgi.com \
    --to=clameter@engr.sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=kiran@scalex86.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@osdl.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