lkml.org 
[lkml]   [1999]   [Jul]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: kernel thread support - LWP's
    Nils Nieuwejaar - Sun High Performance Computing wrote:

    > To switch to an event-based model, that implicit state would have to be
    > explitly saved and restored when processing other events. Depending on
    > the application, that state could be arbitrarily complex, and
    > saving/restoring it could be hard to do quickly and correctly. Once
    > you've written all the save/restore code, you've essentially written your
    > own special-purpose user-level threading library, and each 'event' is
    > really just a 'context switch'.

    In most event based programming state is captured in some form of structure or
    object. When you switch contexts you just point to a different object. Where is
    the high overhead of saving state in that?

    Steve



    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:53    [W:2.147 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site