lkml.org 
[lkml]   [2006]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 01/02] cpuset memory spread slab cache filesys
On Mon, 27 Feb 2006, Andi Kleen wrote:

> I don't quite get your logic here. For me it would be logical to apply
> the memory policy from the process for anything _but_ slab caches
> that have SLAB_MEM_SPREAD set. For those interleaving should be always used.

Interleaving is a special feature to be used only if we know that the
objects are used in a system wide fashion. Interleave should never be the
default option.

F.e. inode interleaving for a process that is running on one
node and scanning files will reduce performance. This is the typical
case.

On the other hand if files are used by multiple processes in a cpuset then
interleaving may be beneficial.

> Why are you proposing to do it the other way round?

Because these are the types of objects that may benefit from
interleaving. Other slabs need to always be allocated in a node local
way.
-
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-28 00:16    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site