[lkml]   [2006]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: + sched-use-tasklet-to-call-balancing.patch added to -mm tree
    On Tue, 7 Nov 2006, Siddha, Suresh B wrote:

    > tasklet_schedule doesn't schedule if there is already one scheduled.


    /* Tasklets --- multithreaded analogue of BHs.

    Main feature differing them of generic softirqs: tasklet
    is running only on one CPU simultaneously.

    Main feature differing them of BHs: different tasklets
    may be run simultaneously on different CPUs.

    * If tasklet_schedule() is called, then tasklet is guaranteed
    to be executed on some cpu at least once after this.

    ^^^^ Crap. Not equivalent. Must be guaranteed to run on the same cpu.

    * If the tasklet is already scheduled, but its excecution is still not
    started, it will be executed only once.
    * If this tasklet is already running on another CPU (or schedule is called
    from tasklet itself), it is rescheduled for later.
    * Tasklet is strictly serialized wrt itself, but not
    wrt another tasklets. If client needs some intertask synchronization,
    he makes it with spinlocks.

    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: 2006-11-07 19:21    [W:0.019 / U:7.620 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site