Re: [patch -mm v2] cpusets: add memory_slab_hardwall fla

[Christoph Lameter]

On Mon, 16 Mar 2009, David Rientjes wrote:

> Here is my example (for the third time) if, for example, mems are grouped
> by the cpus for which they have affinity:

Well I wish I had been send the messages the first two times.

> /dev/cpuset
> 	--> cpuset_A (cpus 0-1, mems 0-3)
> 	--> cpuset_B (cpus 2-3, mems 4-7)
> 	--> cpuset_C (cpus 4-5, mems 8-11)
> 	--> ...

A cpu can only be assigned to a single numa node. cpuset_A/B/C have 2
cpus but 4 nodes. What is the mapping of nodes to cpus?

> Within that, we isolate mems for specific jobs:
>
> /dev/cpuset
> 	--> cpuset_A (cpus 0-1, mems 0-3)
> 		--> job_1 (mem 0)
> 		--> job_2 (mem 1-2)
> 		--> job_3 (mem 3)
> 	--> ...

Nobody would do that since usually multiple cpus are associated with a
single node. Memory and processors are assigned together in order to
reduce latencies. Randomly assigning processors to nodes will cause
latencies and significant traffic on the interconnect. This does not look
sane and would not be optimized in any way.

Are these memoryless nodes? What are you trying to accomplish?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/