lkml.org 
[lkml]   [2007]   [Oct]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch 2/2] cpusets: add interleave_over_allowed option
    > So the user space asks for 8 nodes because it knows the machine
    > has that many from /sys and it only gets 4 if a cpuset says so? That's
    > just bad semantics. And is not likely to make the user programs happy.

    That's no different than what can happen today -- if a task actually
    is in an 8 node cpuset, sets up its mempolicies accordingly, and then
    gets shoe horned into a 4 node cpuset.

    It's not good or bad; it's just interactions between two mechanisms.

    If your app doesn't run well in a small cpuset, don't run it there
    (or do run it there, poorly ;).

    --
    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <pj@sgi.com> 1.925.600.0401
    -
    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: 2007-10-29 23:51    [W:0.021 / U:0.424 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site