[EMAIL PROTECTED] (Linus Torvalds) wrote on 23.10.00 in <[EMAIL PROTECTED]>: > actually inform about the events. The way to do this simply is to limit it > in very clear ways, the most notable one being simply that there is only > one event queue per process (or rather, per "struct files_struct" - so > threads would automatically share the event queue). This keeps the While the rest looks fine, I suspect this one is a show-stopper. IMO, the ability to wait for separate event sets in separate threads is a MUST. In a single-threaded program, it would probably still be useful in a number of situations. Not that it's all that difficult to expand your model to do multiple queues. MfG Kai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Linux's implementatio... Mitchell Blank Jr
- Re: Linux's implementatio... Evan Jeffrey
- Re: Linux's implementatio... Linus Torvalds
- Re: Linux's implementatio... H. Peter Anvin
- Re: Linux's implementatio... Gideon Glass
- Re: Linux's implementatio... Simon Kirby
- Re: Linux's implementatio... Linus Torvalds
- Re: Linux's implementatio... Simon Kirby
- Re: Linux's implementatio... Miquel van Smoorenburg
- Re: Linux's implementatio... Dan Maas
- async IO events Kai Henningsen
- async IO events Ingo Molnar
- Re: Linux's implementatio... Andi Kleen
- Re: Linux's implementation of poll() n... Felix von Leitner
- RE: Linux's implementation of poll() not scalable? David Schwartz
- Re: Linux's implementation of poll() not scalable? Dan Kegel
- Re: Linux's implementation of poll() not scala... Jordan Mendelson
- Re: Linux's implementation of poll() not s... Dan Kegel
- Re: Linux's implementation of poll() n... Dan Kegel
- Re: Linux's implementation of poll... Linus Torvalds
- Linux C++ safe header project Linux Kernel Developer