lkml.org 
[lkml]   [2000]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
torvalds@transmeta.com (Linus Torvalds)  wrote on 23.10.00 in <Pine.LNX.4.10.10010232159480.940-100000@penguin.transmeta.com>:

> 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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:47    [W:0.122 / U:8.968 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site