slice module + thread pools

Vadim Lazovskiy vadim.lazovskiy на gmail.com
Чт Фев 25 17:11:31 UTC 2016


2016-02-25 19:20 GMT+03:00 Maxim Dounin <mdounin at mdounin.ru>:

> Патч:
>
> # HG changeset patch
> # User Maxim Dounin <mdounin at mdounin.ru>
> # Date 1456417157 -10800
> #      Thu Feb 25 19:19:17 2016 +0300
> # Node ID 06da00f231e74bbb8dbb55fd6abd88ca8b207917
> # Parent  463609ba52b07e8e669d83ca7ca7fa754ae5355a
> Fixed sendfile in threads when used with subrequests.
>
> If sendfile in threads where used, it was possible that multiple
> subrequests will trigger multiple ngx_linux_sendfile_thread() calls,
> as operations are only serialized in output chain based on r->aio,
> that is, on subrequest level.
>
> This resulted in "task #N already active" alerts, in particular, when
> running proxy_store.t with "aio threads; sendfile on;".
>
> Fix is to tolerate duplicate calls, with an additional safety check
> that the file is the same as previously used.
>
> diff --git a/src/os/unix/ngx_linux_sendfile_chain.c
> b/src/os/unix/ngx_linux_sendfile_chain.c
> --- a/src/os/unix/ngx_linux_sendfile_chain.c
> +++ b/src/os/unix/ngx_linux_sendfile_chain.c
> @@ -354,6 +354,18 @@ ngx_linux_sendfile_thread(ngx_connection
>          return (ctx->sent == ctx->size) ? NGX_DONE : NGX_AGAIN;
>      }
>
> +    if (task->event.active && ctx->file == file) {
> +        /*
> +         * tolerate duplicate calls with the same file;
> +         * it can happen due to subrequests, as r->aio only serializes
> +         * operations within a single subrequest
> +         */
> +
> +        *sent = 0;
> +
> +        return NGX_OK;
> +    }
> +
>      ctx->file = file;
>      ctx->socket = c->fd;
>      ctx->size = size;
>
>
Максим, спасибо. На первый взгляд патч работает. Завтра попробуем под
нагрузкой.

P.S.: может показаться, что я не умею пользоваться почтой. Похоже, это
действительно так. Прошу меня извинить ;)

-- 
WBR,
Vadim Lazovskiy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-ru/attachments/20160225/50e0b211/attachment.html>


Подробная информация о списке рассылки nginx-ru