Messages in this thread | | | Subject | Re: Linus on Linux, Apache and Threads | From | Andi Kleen <> | Date | 24 Apr 1999 12:51:44 +0200 |
| |
cel@monkey.org (Chuck Lever) writes:
> On Fri, 23 Apr 1999, Tony Gale wrote: > > On 23-Apr-99 Chris Wedgwood wrote: > > >> It ought to one of two things: > > >> > > >> - Use a thread to handle each request, all in one process. > > > > > > No, that would be insane. Perhaps use threads the way it now uses > > > processes, but not one thread per request -- that would be death as > > > far as performance goes. > > > > Depends. You can use a thread pool and queue requests which are then > > picked up by the threads. > > how do you propose to do that efficiently? is there a nice way in > Unix/Linux to hand out incoming network requests to a pool of threads?
You have multiple threads doing an accept on a single listen socket. As soon as a thread finished work it calls accept and gets the next ready connection handed from the kernel.
-Andi
-- This is like TV. I don't like TV.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |