[lkml]   [2002]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [Lse-tech] Re: [PATCH] O(1) scheduler set_cpus_allowed for non-current tasks
    On Wed, 20 Feb 2002, Paul Jackson wrote:

    > I see three levels of synchonization possible here:
    > 1) As Erich did, use IPI to get immediate application
    > 2) Wakeup the target task, so that it will "soon" see the
    > cpus_allowed change, but don't bother with the IPI, or
    > 3) Make no effort to expedite notifcation, and let the
    > target notice its changed cpus_allowed when (and if)
    > it ever happens to be scheduled active again.

    (3) looks good, if the process isn't running it makes little difference on
    which CPU it doesn't run. Would probably be enough to ensure that if it is
    scheduled active the change is noted at that time. "Eventually" is a good
    time to do this, when going through schedule code anyway.

    bill davidsen <>
    CTO, TMR Associates, Inc
    Doing interesting things with little computers since 1979.

    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 13:24    [W:0.023 / U:47.540 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site