email@example.com (Linus Torvalds) wrote on 23.10.00 in <Pine.LNX.firstname.lastname@example.org>:
> 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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 31 2000 - 21:00:15 EST