On Wed, May 23, 2012 at 03:20:11PM -0700, Andrew Morton wrote:
> On Wed, 23 May 2012 13:28:21 +
> Nathan Zimmer wrote:
>
> >
> > When tmpfs has the memory policy interleaved it always starts allocating at
> > each file at node 0.
> > When there are many small files the lower nodes fill up d
On Wed, 23 May 2012 13:28:21 +
Nathan Zimmer wrote:
>
> When tmpfs has the memory policy interleaved it always starts allocating at
> each file at node 0.
> When there are many small files the lower nodes fill up disproportionately.
> My proposed solution is to start a file at a randomly ch
On 05/23/2012 09:28 AM, Nathan Zimmer wrote:
When tmpfs has the memory policy interleaved it always starts allocating at
each file at node 0.
When there are many small files the lower nodes fill up disproportionately.
My proposed solution is to start a file at a randomly chosen node.
Cc: Chris
When tmpfs has the memory policy interleaved it always starts allocating at
each file at node 0.
When there are many small files the lower nodes fill up disproportionately.
My proposed solution is to start a file at a randomly chosen node.
Cc: Christoph Lameter
Cc: Nick Piggin
Cc: Hugh Dickins
When tmpfs has the memory policy interleaved it always starts allocating at
each file at node 0.
When there are many small files the lower nodes fill up disproportionately.
My proposed solution is to start a file at a randomly chosen node.
Cc: Christoph Lameter
Cc: Nick Piggin
Cc: Hugh Dickins
