[lkml]   [2010]   [May]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH/RFC] Have sane default values for cpusets
    On Wed, May 12, 2010 at 12:10 PM, Dhaval Giani <> wrote:
    > On Wed, May 12, 2010 at 9:01 PM, Paul Menage <> wrote:
    >> What about the case where some subset of the parent's mems/cpus are
    >> given to a child with the exclusive flag set?
    > As I mentioned in the TODO, it is still to be handled.

    Oops, sorry, just read the patch :-)

    > But it should
    > simply exclude those mems/cpus which are exclusive. It was a bit more
    > involved than the effort I wanted to put in before gauging the
    > reactions.

    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.


     \ /
      Last update: 2010-05-12 21:23    [W:0.029 / U:34.480 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site