On Tue, 2006-08-22 at 16:46 -0700, Ulrich Drepper wrote: > I so far also haven't taken the time to look exactly at the interface. > I plan to do it asap since this is IMO our big chance to get it right. > I want to have a unifying interface which can handle all the different > events we need and which come up today and tomorrow. We have to be able > to handle not only file descriptors and AIO but also timers, signals, > message queues (OK, they are file descriptors but let's make it > official), futexes. I'm probably missing the one or the other thing now.
Are you sure about signals? I thought about that, but they generally fall into two categories: signals that have to be signals (i.e. SIGILL, SIGABRT, SIGFPE, SIGSEGV, etc.) and signals that should be replaced a queued event notification (SIGALRM, SIGRTMIN-SIGRTMAX). Of course, that leaves things like SIGTERM, SIGINT, SIGQUIT, etc. so, uh, nevermind then. Signal redirection to event queues is definitely needed. > DaveM says there are example programs for the current interfaces. I > must admit I haven't seen those either. So if possible, point the world > to them again. If you do that now I'll review everything and write up > my recommendations re the interface before Monday. There's a handful of little test apps at http://tservice.net.ru/~s0mbre/archive/kevent/ , but they don't work with the current iteration of the interface. I don't know if there are others somewhere else. -- Nicholas Miell <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
