lkml.org 
[lkml]   [2002]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: O(1) scheduler "complex" macros

    the best solution might be to just lock the 'next' task - this needs a new
    per-task irq-safe spinlock, to avoid deadlocks. This way whenever a task
    is in the middle of a context-switch it cannot be scheduled on another
    CPU.

    in fact this solution simplifies things - only two per-arch macros are
    needed. I've done this in my current 2.5.25 tree:

    http://redhat.com/~mingo/O(1)-scheduler/sched-2.5.25-A4

    check out the sparc64 changes for the 'complex' locking scenario - it's
    untested, please give it a go on ia64, does that solve your problems? x86
    is tested and works just fine.

    Ingo

    -
    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 13:27    [W:0.050 / U:0.204 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site