[lkml]   [1999]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linus on Linux, Apache and Threads
> 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?

Huh? It's not that hard of a problem. You have one (or several) thread
that just reads from network sockets. They package up the requests and put
them on the end of a queue. The other threads just pull requests off the
head of the queue. The trick is all in waking up the sleeping threads when
the queue becomes non-empty without having the "thundering herd" problem.

It is even possible, if you have only one thread adding to the queue, to
implement the queue so that the writing thread doesn't need a lock. Only
the reading threads need a lock. If you have multiple writing threads you
would need a read lock and a write lock. This enables massive amounts of
concurency, and is a huge win on mp systems.
"With a touch more confidence and a liberal helping of ignorance I would have
been a famous evangelist."
-- Stranger In A Strange Land
PLENTY of ignorance at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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