On Tue, 2 Oct 2007, KAMEZAWA Hiroyuki wrote: > For fujitsu, problem is called "empty" node. Future SGI platforms (actually also current one can have but nothing like that is deployed to my knowledge) have nodes with only cpus. Current SGI platforms have nodes with just I/O that we so far cannot manage in the core. So the arch code maps them to the nearest memory node. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- -mm merge plans for 2.6.24
- From: Andrew Morton <[email protected]>
- x86 patches was Re: -mm merge plans for 2.6.24
- From: Andi Kleen <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: Andrew Morton <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: Andi Kleen <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: Andrew Morton <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: Andrew Morton <[email protected]>
- Re: x86 patches was Re: -mm merge plans for 2.6.24
- From: KAMEZAWA Hiroyuki <[email protected]>
- -mm merge plans for 2.6.24
- Prev by Date: Re: x86 patches was Re: -mm merge plans for 2.6.24
- Next by Date: Re: [HACK] convert i_alloc_sem for direct_io.c craziness!
- Previous by thread: Re: x86 patches was Re: -mm merge plans for 2.6.24
- Next by thread: Re: x86 patches was Re: -mm merge plans for 2.6.24
- Index(es):
 |