Aaron Bannert wrote: [...] >The hard part about this (at least for me) is the multitude of variables >that go in to deciding the implementation of the accept() mutex. Is there >a way I can find out (at runtime) what implementation is being used? > If you're willing to use external instrumentation (as opposed to having the httpd deduce the mechanism by itself at runtime), you can figure out the accept serialization method with truss. (The -l arg to truss, if I remember correctly, will show the LWP ID for each syscall, so you can look for the last syscall that each LWP does before accept.) --Brian
- OSDLab projectL Accept() locking on large (6+ CPU) b... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on large (... Aaron Bannert
- Re: OSDLab projectL Accept() locking on lar... Brian Pane
- Re: OSDLab projectL Accept() locking on... Aaron Bannert
- Re: OSDLab projectL Accept() lockin... Brian Pane
- Re: OSDLab projectL Accept() lockin... Bill Stoddard
- Re: OSDLab projectL Accept() lockin... Jeff Trawick
- Re: OSDLab projectL Accept() locking on... Justin Erenkrantz
- Re: OSDLab projectL Accept() lockin... Aaron Bannert
- Re: OSDLab projectL Accept() locking on large (... Bill Stoddard
- Re: OSDLab projectL Accept() locking on lar... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on... Ian Holsman
- Re: OSDLab projectL Accept() lockin... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on large (... Ben Hyde
