Re: [patch 2/4] mempolicy: support optional mode flags
From: David Rientjes
Date: Tue Feb 12 2008 - 14:18:42 EST
On Tue, 12 Feb 2008, Lee Schermerhorn wrote:
> Hmmm, so 'static' means "don't contexutalize"--i.e., don't mask off
> disallowed or memoryless nodes? That means we'll need to skip them in
> the interleave node calculation in the allocation path. Perhaps your
> patch already addresses this, but I haven't had time to look.
All MPOL_F_STATIC_NODES does (by mbind(), set_mempolicy(), or adding
'=static' to the mempolicy mode on tmpfs mount) is suppress the node remap
In mpol_new(), the intent of the user is stored in a new nodemask_t member
of struct mempolicy and in the static case the passed nodemask is
intersected with that member. The policy is then effected over the
If that nodemask includes no accessible nodes, then the mempolicy is not
effected but rather lies dormant until access to those nodes is attained.
If and when that happens, the mempolicy will then be effected again
without any additional set_mempolicy() or mbind() from the user.
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/