lkml.org 
[lkml]   [2003]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: fairsched + O(1) process scheduler
    From
    Date
    On Wed, 2003-04-02 at 16:36, Antonio Vargas wrote:

    > I've been thinking about this thing a while ago, and I think I could do this:
    >
    > a. Have a kernel thread which wakes up on each tick.

    Why not use the timer tick itself? It already calls scheduler_tick()...

    Oh, because you need to grab uidhash_lock? Ew. Needing a kernel thread
    for this is not pretty.

    > Also, this locking rule means I can't even read current->user->time_slice?
    > What if I changed the type to an atomic_int?

    You can always read a single word-sized type atomically. No need for
    atomic_t's.

    Robert Love

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