Re(4): Proper time to thread?
Re(4): Proper time to thread?
- Subject: Re(4): Proper time to thread?
- From: Jens Bauer <email@hidden>
- Date: Sat, 1 Jun 2002 12:33:04 +0200
Hi Jason and Duane,
Thankyou both for clearing up these things. :)
So in fact, using select() from a thread, you don't have to bittest a
list of sockets to find out which socket the event occurred on, if you
just have one socket for this thread ?
-Say you have 10 sockets, spawn 10 threads and you'll be sure that each
select receives the event for the right socket ?
If this is the case, I can imagine how fast it is, because the CPU then
only has to restore the thread registers (including the stack pointer,
a'la setjmp) to go directly to where we're awaiting the event, rather
than returning through a general event-handler, where we have to test
conditions first.
On Fri, 31 May, 2002, Duane Murphy <email@hidden> wrote:
>
Open Transport on X does not do real interrupt driven events.
>
They are entirely simulated.
On Fri, 31 May, 2002, Jason Linhart <email@hidden> wrote:
>
I have not seen the OpenTransport glue code, but I strongly suspect that
>
they are using a thread calling select to trigger notifiers.
Love,
Jens
--
Jens Bauer, Faster Software.
-Let's make the World better, shall we ?
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.