lkml.org 
[lkml]   [2005]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4)
    Dave wrote:
    > Shouldn't a particular task know what the policy should be when it is
    > launched?

    No ... but not necessarily because it isn't known yet, but rather also
    because it might be imposed earlier in the job creation, before the
    actual task hierarchy is manifest. This point goes to the heart of one
    of the motivations for cpusets themselves.

    On a big system, one might have OpenMP threads inside MPI tasks inside
    jobs being managed by a batch manager, running on a subset of the
    system. The system admins may need to impose these policy decisions
    from the outside, and not uniformly across the entire batch managed
    arena. The cpuset becomes the named object, to which such attributes
    accrue, to take affect on whatever threads, tasks, or jobs end up
    thereon.

    Do a google search for "mixed openmp mpi", or for "hybrid openmp mpi",
    to find examples of such usage, then imagine such jobs running inside a
    batch manager, on a portion of a larger system.

    --
    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 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: 2005-03-22 14:11    [W:6.441 / U:0.092 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site