lkml.org 
[lkml]   [2006]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Avoid allocating during interleave from almost full nodes
On Mon, 6 Nov 2006, Andrew Morton wrote:

> But doesn't this patch introduce considerable risks of the above problems
> occurring? In the two-nodes-have-lots-of-free-memory scenario?

If two nodes have lots of memory then we will alternate between both
nodes. If one of the nodes is going below the interleave limit then we
will indeed only allocate from that single node. At some point both are
dropping below the limit and we will revert back to alternating.

We can avoid the phase where we only allocate from one node by checking
the node weight of the available nodes instead of checking for an empty
node mask.

For systems with less than 3 nodes the approach will not be useful. What I
had in mind when writing this patch were systems with a large number of
nodes segmented by cpusets into smaller slices. The segments would
still be greater than 4 nodes.
-
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-11-06 22:45    [W:0.042 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site