Re: Help with shared memory usage

Hello Maxim, I changed the patch to check only the p->next pointer. And checking if the page is in an address less than the (pool->pages + pages). +ngx_slab_page_t *prev, *p; +ngx_uint_tpages; +size_tsize; + +size = pool->end - (u_char *) pool - sizeof(ngx_slab

[nginx] SPDY: a bit smarter ngx_http_spdy_filter_get_data_frame().

details: http://hg.nginx.org/nginx/rev/97f6cd787766 branches: changeset: 5495:97f6cd787766 user: Valentin Bartenev date: Thu Dec 26 17:03:16 2013 +0400 description: SPDY: a bit smarter ngx_http_spdy_filter_get_data_frame(). There is no need to pass FLAG_FIN as a separate argument si

[nginx] SPDY: refactored loop in ngx_http_spdy_body_filter().

details: http://hg.nginx.org/nginx/rev/27f9d5f68c1c branches: changeset: 5494:27f9d5f68c1c user: Valentin Bartenev date: Thu Dec 26 17:03:16 2013 +0400 description: SPDY: refactored loop in ngx_http_spdy_body_filter(). No functional changes. diffstat: src/http/ngx_http_spdy_filte

[nginx] SPDY: fixed possible request hang.

details: http://hg.nginx.org/nginx/rev/916cb6d28f6a branches: changeset: 5493:916cb6d28f6a user: Valentin Bartenev date: Thu Dec 26 17:03:16 2013 +0400 description: SPDY: fixed possible request hang. Processing events from upstream connection can result in sending queued frames from