On 25.09.2006 16:43, Garrett Rooney wrote: > On 9/25/06, Ruediger Pluem <[EMAIL PROTECTED]> wrote: > >> On 25.09.2006 16:32, Garrett Rooney wrote: >> > On 9/25/06, Jim Jagielski <[EMAIL PROTECTED]> wrote: >> > >> >> Actually, I've added the 'busy' struct element which >> >> could be used for that... The orig intent was to add >> >> the mod_jk "busyness" LB method, but it would also >> >> serve as a flag that the member is busy ;) >> >> >> >> As of now, neither Trunk or 2.2.x do anything with busy, >> >> but that will change soon :) >> > >> > >> > How is that flag shared across worker processes? Is that structure >> > stored in shared memory or something? >> >> It is shared via the scoreboard along with all other worker >> interprocess data >> like status of the worker etc. > > > Ahh, cool. That will come in handy for the fastcgi stuff if I ever > get back to it...
After having a look in the code I am just wondering why we do not have any locks around when changing this shared data / do not use atomics when increasing e.g the value for the number of read bytes (worker->s->read). Is this correct? Regards Rüdiger
