Messages in this thread | | | Date | Fri, 16 Jul 1999 02:46:15 +0000 | From | Steve Underwood <> | Subject | Re: 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/
| |