In message <20020906.124936.34476547.davem@xxxxxxxxxx>, > : "David S. Miller" w
> From: Gerrit Huizenga <gh@xxxxxxxxxx>
> Date: Fri, 06 Sep 2002 12:52:15 -0700
> So if apache were using a listen()/clone()/accept()/exec() combo rather
> than a
> full listen()/fork()/exec() model it would see most of the same benefits?
> Apache would need to do some more, such as do something about
> cpu affinity and do the non-blocking VFS tricks Tux does too.
> To be honest, I'm not going to sit here all day long and explain how
> Tux works. I'm not even too knowledgable about the precise details of
> it's implementation. Besides, the code is freely available and not
> too complex, so you can go have a look for yourself :-)
Aw, and you are such a good tutor, too. :-) But thanks - my particular
goal isn't to fix apache since there is already a group of folks working
on that, but as we look at kernel traces, this should give us a good
idea if we are at the bottleneck of the apache architecture or if we
have other kernel bottlenecks. At the moment, the latter seems to be
true, and I think we have some good data from Troy and Dave to validate
that. I think we have already seen the affinity problem or at least
talked about it as that was somewhat visible and Apache 2.0 does seem
to have some solutions for helping with that. And when the kernel does
the best it can with Apache's architecture, we have more data to convince
them to fix the architecture problems.