lkml.org 
[lkml]   [2006]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/5] cpuset memory spread basic implementation
Ingo asked:
> so in practice, the memory spreading is in fact a global setting, used
> by all cpusets that matter?

I don't know if that is true or not.

I'll have to ask my field engineers, who actually have experience
with a variety of customer workloads.

... well, I do have partial knowledge of this.

When I was coding this, I suggested that instead of picking some of the
slab caches to memory spread, we pick them all, as that would be easier
to code.

That suggestion was shot down by others more experienced within SGI, as
some slab caches hold what is essentially per-thread data, that is
fairly hot in the thread context that allocated it. Spreading that data
would quite predictably increase cross-node bus traffic, which is bad.

--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-02-06 09:50    [from the cache]
©2003-2011 Jasper Spaans