:
:phhttpd does this by changing who the sigio signal for incoming accepts
:gets delivered too.. after each accept it is handed to the next thread.
:
:-- zach
Ugh. SIGIO is evil and should never be used. I tried using SIGIO for
tty I/O many years ago and it was a total disaster - it used an
unbelievable amount of cpu due to the signal overhead :-)
I theoretically own the rights to BestWWWD if only I could find the piece
of paper. It shouldn't be an issue any longer with Best/Verio, I'll see
what can be done.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: mbuf wait code (revisited) -- review? Bosko Milekic
- Re: mbuf wait code (revisited) -- review? Remy Nonnenmacher
- Re: mbuf wait code (revisited) -- review? David Greenman
- Re: mbuf wait code (revisited) -- review? Matthew Dillon
- Re: mbuf wait code (revisited) -- rev... Bosko Milekic
- Re: mbuf wait code (revisited) -... Matthew Dillon
- Re: mbuf wait code (revisited) -... Bosko Milekic
- Re: mbuf wait code (revisited) -- review? Zach Brown
- Re: mbuf wait code (revisited) -- rev... Matthew Dillon
- Re: mbuf wait code (revisited) -... Zach Brown
- Re: mbuf wait code (revisited) -... Matthew Dillon
- Re: mbuf wait code (revisited) -... Zach Brown
- Re: mbuf wait code (revisited) -... Jonathan M. Bresler
- Re: mbuf wait code (revisited) -... Tony Finch
- Re: mbuf wait code (revisited) -... Matthew Dillon
- Re: mbuf wait code (revisited) -- rev... Remy Nonnenmacher
- Re: mbuf wait code (revisited) -- review? Kip Macy

