Forgive me if this has been beaten to death here or in other forums. In apache 1.3 you can set SINGLE_LISTEN_UNSERIALIZED_ACCEPT to tell apache not to put some sort of mutex around the accept() call. This mutex was ostensibly required so that apache's multiple process children did not wake up on each request from the kernel. Is this kind of mutex still necessary in DFly? If not, why not? Thanks in advance. ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.orgIf you have the idea of superiority and are proud of your ability, this is a disaster.
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Christoph Hellwig | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scan... |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Emmanuel Dreyfus | fixing send(2) semantics (kern/29750) |
| Christos Zoulas | Re: Melting down your network [Subject changed] |
| Juan RP | Changing the I/O scheduler on-the-fly |
| Emmanuel Dreyfus | Re: fixing send(2) semantics (kern/29750) |
