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

[Andrew Morton]

Andrew Morton <akpm@xxxxxxxx> wrote:
>
> Paul Jackson <pj@xxxxxxx> wrote:
>  >
>  > From: Paul Jackson <pj@xxxxxxx>
>  > 
>  > This patch provides the implementation and cpuset interface for
>  > an alternative memory allocation policy that can be applied to
>  > certain kinds of memory allocations, such as the page cache (file
>  > system buffers) and some slab caches (such as inode caches).
>  > 
>  > ...
>  >
>  > A new per-cpuset file, "memory_spread", is defined.  This is
>  > a boolean flag file, containing a "0" (off) or "1" (on).
>  > By default it is off, and the kernel allocation placement
>  > is unchanged.  If it is turned on for a given cpuset (write a
>  > "1" to that cpusets memory_spread file) then the alternative
>  > policy applies to all tasks in that cpuset.
> 
>  I'd have thought it would be saner to split these things apart:
>  "slab_spread", "pagecache_spread", etc.

This, please.   It impacts the design of the whole thing.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/