[lkml]   [2000]   [Dec]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux 2.2.19pre and thttpd (VM-global problem?)
On Fri, 29 Dec 2000, Daniel R. Kegel wrote:

> Andrea Arcangeli wrote:
> > Petru Paler wrote:
> > > This is one of the main thttpd design points: run in a select() loop. Since
> > > it is intended for mainly static workloads, it performs quite well...
> >
> > It can't scale in SMP.
> thttpd is i/o bound, not CPU bound, so there's no need for SMP scaling.
> It's an effective little server as long as the active document
> tree fits in RAM.
> If it ain't broke, don't tell people how to fix it :-)
> (If for some reason SMP scaling was desirable, the thttpd
> way to do it would be to introduce one thread for each
> CPU, and have each thread run the same select() loop.)

One could possibly cheat and use fork() instead of using threads.
Do your listen() before forking..then both get the listener socket..
Threads aren't always the answer, in this case it wouldn't probably gain
you anything over just doing a fork() on SMP. Especially if you got not
good reason to be sharing data that closely, which I don't think thttpd


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 12:52    [W:0.027 / U:0.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site