Messages in this thread | | | From | "H. Peter Anvin" <> | Date | 24 Oct 2000 17:13:51 -0700 |
| |
Followup to: <Pine.LNX.4.10.10010241559280.826-100000@penguin.transmeta.com> By author: Linus Torvalds <torvalds@transmeta.com> In newsgroup: linux.dev.kernel > > Oh, I agree. > > And I think something like CLONE_EVENTS would be fine - and decide > yourself what kind of threads you want (do you want indistinguishable > "anonymous" threads like apache, or do you want a threads that handle > separate event queues). Or you might have a mixture of the two - for web > serving the "accept()" event list might be a separate thing with a few > threads doing that, while "worker threads" handle the actual IO.. > > But if you want to have some event queue ID, I just wonder how you'd set > it up sanely without tons of complications.. >
How about handle the event queue ID as an event mask internally?
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/
| |