Re: [PATCH 1/5] cpuset memory spread basic implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 6 Feb 2006, Andi Kleen wrote:

> I still don't quite agree. As long as the latency penalty of going
> off node is not too bad (let's say < factor 2) i think it's better
> to spread out the caches than to always locate them locally.

AFAIK you can reach these low latency factors only if multiple nodes are 
on the same motherboard. Likely Opteron specific?

> If you have a much worse worst case NUMA factor it might be different,
> but even there it would be a good idea to at least spread it out
> to nearby nodes.

I dont understand you here. What would be the benefit of selecting more 
distant memory over local? I can only imagine that this would be 
beneficial if we know that the data would be used later by other 
processes.
-
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/

[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]
  Powered by Linux