Re: [PATCH 1/5] try parent numa_node at first before using default

Yinghai Lu wrote:
> original default is -1, and this patch just try to use parent's node as
> default.

But in many cases, the patch does so at a time when the parent is not
yet known.
-- 
Stefan Richter
-=====-=-=== -=== -==--
http://arcgraph.de/sr/
-
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/

Follow-Ups:
- Re: [PATCH 1/5] try parent numa_node at first before using default
  - From: Yinghai Lu <[email protected]>

References:
- [PATCH 1/5] try parent numa_node at first before using default
  - From: Yinghai Lu <[email protected]>
- Re: [PATCH 1/5] try parent numa_node at first before using default
  - From: Stefan Richter <[email protected]>
- Re: [PATCH 1/5] try parent numa_node at first before using default
  - From: Greg KH <[email protected]>
- Re: [PATCH 1/5] try parent numa_node at first before using default
  - From: Yinghai Lu <[email protected]>

Prev by Date: Re: lguest, Re: -mm merge plans for 2.6.23
Next by Date: Re: lguest, Re: -mm merge plans for 2.6.23
Previous by thread: Re: [PATCH 1/5] try parent numa_node at first before using default
Next by thread: Re: [PATCH 1/5] try parent numa_node at first before using default
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]