On Thursday 10 April 2014 04:32:42 nginxsantos wrote:
> Thank you.
> But, my question is when we are allocating a pool of more than one page size
> why are we putting the max value as one page size and then further leading
> to memory allocation.
>
Because there are no advantages in allocating bi
Thank you.
But, my question is when we are allocating a pool of more than one page size
why are we putting the max value as one page size and then further leading
to memory allocation.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249161,249189#msg-249189
_
On Wed, Apr 09, 2014 at 08:31:29AM -0400, nginxsantos wrote:
> Suppose, I am allocating a pool of greater than 4k(page size). Say for
> example I am calling the function ngx_create_pool with 8096.
> But, this function will set the max as 4095 even if it has allocated 8K. Not
> sure, why is it being
Any expert opinions???
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249161,249185#msg-249185
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Suppose, I am allocating a pool of greater than 4k(page size). Say for
example I am calling the function ngx_create_pool with 8096.
But, this function will set the max as 4095 even if it has allocated 8K. Not
sure, why is it being done like this.
p->max = (size < NGX_MAX_ALLOC_FROM_POOL) ? siz
