ink about handling it.
Thanks,
-Ravi.
On Thu, Jan 16, 2014 at 8:04 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Jan 16, 2014 at 07:16:50PM -0800, Ravi Chunduru wrote:
>
> > Hi Maxim,
> > I understand on array overflow nginx creates a new memory block. That
> is
> &
hanks,
-Ravi.
On Thu, Jan 16, 2014 at 6:40 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Jan 16, 2014 at 06:22:58PM -0800, Ravi Chunduru wrote:
>
> > Hi Nginx experts,
> > Thanks for the prompt reply to my earlier email on ngx_reset_pool()
> >
> > Now, I am look
A little correction, a->pool is nothing to do with pool->current. But array
need to have a pointer to pool data of that of memory block that holds the
array elements. Then all checks done in ngx_array_push() etc., will be
correct.
On Thu, Jan 16, 2014 at 6:22 PM, Ravi Chunduru wrote:
Hi Nginx experts,
Thanks for the prompt reply to my earlier email on ngx_reset_pool()
Now, I am looking into ngx_array.c. I found an issue ngx_array_push(). Here
are the details.
nginx will check if number of elements is equal to capacity of the array.
If there is no space in the memory block, i
at 4:07 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Jan 16, 2014 at 02:56:53PM -0800, Ravi Chunduru wrote:
>
> > Hi Nginx experts,
> > I am new to nginx and started looking into the code to understand the
> > architecture.
> >
> > Currently, I am look
Hi Nginx experts,
I am new to nginx and started looking into the code to understand the
architecture.
Currently, I am looking into nginx pool implementation. I have a question
on ngx_reset_pool().
It seems to set back 'last' to the location as expected. But why 'current'
and 'failed' are not res
