| |||||||||||||
I want some of them callbacks!I want some of them callbacks!Posted Oct 31, 2002 13:24 UTC (Thu) by IkeTo (subscriber, #2122)In reply to: I want some of them callbacks! by zooko Parent article: sys_epoll - making poll fast Hmm... that seems to be as difficult to use as signals. The function that you want to use is never in the list of async signal-safe functions, and you application will always have race condition using signals unless your application uses the call in a very limited way: your main application must do basically nothing, and your application must block basically every signal (and wait for signals using sigwait() or sigsuspend()). That means... you'll have to create system calls similar to those to deal with signals, and then to setup a huge size set for suspending file descriptor callbacks. Not to mention that pushing some code to the user is not something that a kernel developers would like to do unless absolutely needed. Doesn't seem to be exactly exciting for this type of optimization which is constant-time anyway.
(Log in to post comments)
I want some of them callbacks! Posted Oct 31, 2002 20:56 UTC (Thu) by zooko (subscriber, #2589) [Link] I think there is an interesting disconnect between the low-level hackers and the higher level network/application level hackers here. A lot of the interesting projects that I know of (not to mention the ones that I lead myself: Mnet), use select()/poll() interfaces exactly as I've described above -- as nothing more than a way to get at the callbacks which they then immediately de-multiplex back into callbacks. The projects I'm thinking of here are things like Twisted, and E (although the current E implementation doesn't use kernel calls, as it is in Java...). Regards, Zooko
I want some of them callbacks! Posted Nov 2, 2002 21:15 UTC (Sat) by bronson (subscriber, #4806) [Link] Maybe IkeTo gave too comprehensive an answer...Is it too tricky to have the kernel change to user context and invoke a function pointer that I have given it? Yes. Whenever the kernel calls user code directly, non-obvious and non-trivial race conditions result. It's a very difficult problem. Much easier to just have the system call return, and then the user can deal with the callbacks however she/he wants.
|
|||||||||||||