Le 20/12/2010 20:06, Guy Streeter a écrit :
> I decided I should just give you the whole output.
Thanks. Indeed, it's a Linux "feature". When you request a non-strict
memory binding in Linux (MPOL_PREFERRED, not MPOL_BIND), it only keeps
the first node in the input nodemask. Instead of allocating on X,Y,Z
when possible and anywhere else otherwise, it allocates on X when
possible and anywhere else otherwise.
That's why we get 0x0000003f (first node cpuset) instead of 0x00ffffff
(four first nodes cpuset) when we request the current binding.