Sent by Bird Mail___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Thanks agentzh, Maxim and Igor
On Tue, Jun 3, 2014 at 11:00 AM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Jun 02, 2014 at 08:42:50PM +0400, Maxim Dounin wrote:
>
> > Hello!
> >
> > On Sat, May 31, 2014 at 11:46:28PM -0300, Wandenberg Peixoto wrote:
> >
> > > Hello Maxim,
> > >
> > > I executed m
Hello!
On Mon, Jun 02, 2014 at 08:42:50PM +0400, Maxim Dounin wrote:
> Hello!
>
> On Sat, May 31, 2014 at 11:46:28PM -0300, Wandenberg Peixoto wrote:
>
> > Hello Maxim,
> >
> > I executed my tests again and seems that your improved patch version is
> > working fine too.
>
> Good, thanks for t
Hello!
On Sat, May 31, 2014 at 11:46:28PM -0300, Wandenberg Peixoto wrote:
> Hello Maxim,
>
> I executed my tests again and seems that your improved patch version is
> working fine too.
Good, thanks for testing.
> Did you plan to merge it on nginx core soon?
It's currently waiting for Igor's
Hi Maxim!
On Wed, May 28, 2014 at 11:38 AM, Maxim Dounin wrote:
>
> Below is a patch which does mostly the same without introducing
> any additional per-page fields. Please take a look if it works
> for you.
>
Thank you for looking into this!
I've run my local test suite for this issue against
Hello Maxim,
I executed my tests again and seems that your improved patch version is
working fine too.
Did you plan to merge it on nginx core soon?
-agentzh
Did you have opportunity to check if it works for you?
Regards
On Wed, May 28, 2014 at 3:38 PM, Maxim Dounin wrote:
> Hello!
>
> On
Hello!
On Sun, May 11, 2014 at 10:13:52PM -0700, Yichun Zhang (agentzh) wrote:
> Hello!
>
> On Mon, Jul 29, 2013 at 10:11 AM, Maxim Dounin wrote:
> > Additionally, doing a full merge of all free blocks on a free
> > operation looks too much. It might be something we want to do on
> > allocation
Hello!
On Mon, Jul 29, 2013 at 10:11 AM, Maxim Dounin wrote:
> Additionally, doing a full merge of all free blocks on a free
> operation looks too much. It might be something we want to do on
> allocation failure, but not on a normal path in
> ngx_slab_free_pages(). And/or something lightweight