[lkml]   [2006]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    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

    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
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-28 00:16    [W:0.022 / U:50.264 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site