Re: [PATCH/RFC] Have sane default values for cpusets

[Paul Menage]

On Wed, May 12, 2010 at 12:29 PM, Dhaval Giani <dhaval.giani@xxxxxxxxx> wrote:
>> I think the idea is reasonable - the only way that I could see it
>> breaking someone would be code that currently does something like:
>>
>> mkdir A
>> mkdir B
>> echo 1 > A/mem_exclusive
>> echo 1 > B/mem_exclusive
>> echo $mems_for_a > A/mems
>> echo $mems_for_b > B/mems
>>
>> The attempts to set the mem_exclusive flags would fail, since A and B
>> would both have all of the parent's mems.
>>
>
> But would this not fail otherwise?
>

Assuming that mems_for_a and mems_for_b were disjoint, it would be
fine currently.

Paul
--
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/