> i'm guessing from your description that the missed event will be noticed
> when the next socket arrives. i.e. if the server is pretty busy then the
> missed events are not important. but if it's not a busy server, like a
> hit every hour, then the missed event may be noticeable to browsers
On Wed, May 16, 2001 at 10:25:32AM -0700, dean gaudet wrote:
> On Wed, 16 May 2001, Andrea Arcangeli wrote:
>
> > On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
> > > apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
> >
> > That's definitely a good thing.
>
>
On Wed, 16 May 2001, Andrea Arcangeli wrote:
> On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
> > apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
>
> That's definitely a good thing.
hmm, i'm not so sure -- 1.3.x is our stable release, and it sounds like
this
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
> On Tue, 15 May 2001, Andrea Arcangeli wrote:
>
> > o fixed race in wake-one LIFO in accept(2). Apache must be compiled with
> > -DSINGLE_LISTEN_UNSERIALIZED_ACCEPT to take advantage of that.
> >
> > 00_wake-one-4
> >
> >
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
On Tue, 15 May 2001, Andrea Arcangeli wrote:
o fixed race in wake-one LIFO in accept(2). Apache must be compiled with
-DSINGLE_LISTEN_UNSERIALIZED_ACCEPT to take advantage of that.
00_wake-one-4
Backport 2.4
On Wed, 16 May 2001, Andrea Arcangeli wrote:
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
That's definitely a good thing.
hmm, i'm not so sure -- 1.3.x is our stable release, and it sounds like
this
On Wed, May 16, 2001 at 10:25:32AM -0700, dean gaudet wrote:
On Wed, 16 May 2001, Andrea Arcangeli wrote:
On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...
That's definitely a good thing.
hmm, i'm not
i'm guessing from your description that the missed event will be noticed
when the next socket arrives. i.e. if the server is pretty busy then the
missed events are not important. but if it's not a busy server, like a
hit every hour, then the missed event may be noticeable to browsers (as a
On Tue, 15 May 2001, Andrea Arcangeli wrote:
> o fixed race in wake-one LIFO in accept(2). Apache must be compiled with
> -DSINGLE_LISTEN_UNSERIALIZED_ACCEPT to take advantage of that.
>
> 00_wake-one-4
>
> Backport 2.4 waitqueues and in turn fixes an hanging condition in
On Tue, 15 May 2001, Andrea Arcangeli wrote:
o fixed race in wake-one LIFO in accept(2). Apache must be compiled with
-DSINGLE_LISTEN_UNSERIALIZED_ACCEPT to take advantage of that.
00_wake-one-4
Backport 2.4 waitqueues and in turn fixes an hanging condition in accept(2).
10 matches
Mail list logo