[lkml]   [2004]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ckrm-tech] Re: [Lse-tech] [PATCH] cpusets - big numa cpu and memory placement
    Hubertus writes:
    > Since classes can span different cpu sets with different shares
    > how do we address the cpushare of a class in the particular context
    > of a cpu-set.
    > Alternatively, one could require that classes can not span different
    > cpu-sets, which would significantly reduce the complexity of this.

    It's not just cpusets that sets a tasks cpus_allowed ...

    Lets say we have a 16 thread OpenMP application, running on a cpuset of
    16 CPUs on a large system, one thread pinned to each CPU of the 16 using
    sched_setaffinity, running exclusively there. Which means that there
    are perhaps eight tasks pinned on each of those 16 CPUs, the one OpenMP
    thread, and perhaps seven indigenous per-cpu kernel threads:
    migration, ksoftirq, events, kblockd, aio, xfslogd and xfsdatad
    (using what happens to be on a random 2.6 Altix in front of me).

    Then the classe(s) containing the eight tasks on any given one of these
    CPUs would be required to not contain any other tasks outside of those
    eight, by your reduced complexity alternative, right?

    On whom/what would this requirement be imposed? Hopefully some CKRM
    classification would figure this out and handle the classification

    What of the couple of "mother" tasks in this OpenMP application, which
    are in this same 16 CPU cpuset, probably pinned to all 16 of the CPUs,
    instead of to any individual one of them? What are the requirements on
    the classes to which these tasks belong, in relation to the above
    classes for the per-cpu kthreads and per-cpu OpenMP threads? And on
    what person/software is the job of adapting to these requirements

    Observe by the way that so long as:
    1) the per-cpu OpenMP threads each get to use 99+% of their
    respective CPUs,
    2) CKRM didn't impose any constraints or work on anything else

    then what CKRM does here doesn't matter.

    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <> 1.650.933.1373
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:06    [W:0.052 / U:95.460 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site