Stefan Richter wrote:
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.
then it will use -1. YH - 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: Stefan Richter <[email protected]>
- Re: [PATCH 1/5] try parent numa_node at first before using default
- 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]>
- Re: [PATCH 1/5] try parent numa_node at first before using default
- From: Stefan Richter <[email protected]>
- [PATCH 1/5] try parent numa_node at first before using default
- Prev by Date: Re: [PATCH 1/2] SCHED: Generic hooks for trapping task preemption
- Next by Date: Re: [PATCH 24/61] sysfs: make sysfs_put() ignore NULL sd
- 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):
 |