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 Molnar <mingo@elte.hu> wrote:

> > We normally run with different policies, in the same box, on different
> > cpusets at the same time. But this might be because some cpusets
> > -need- the memory spreading, and the others that don't are left to the
> > default policy.
>
> so in practice, the memory spreading is in fact a global setting, used
> by all cpusets that matter? That seems to support Andrew's observation
> that our assumptions / defaults are bad, pretty much independently of
> the workload.

in other words: the spreading out likely _hurts_ performance in the
typical case (which prefers node-locality), but when you are using
multiple cpusets you want to opt for fairness between projects, over
opportunistic optimizations such as node-local allocations. I.e. the
spreading out, as it is used today, is rather a global fairness setting
for the kernel, and not really a workload-specific access-pattern thing.
Right?

Ingo
-
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:44    [W:0.018 / U:0.540 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site