Date: Thu, 11 Jul 2013 02:39:00 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: hacking - aio_sendfile() Message-ID: <CAJ-Vmo=ic_KuaaE2avvbX3JE=R25nuRyyAQpEmFrZRp7T9y9qg@mail.gmail.com> In-Reply-To: <20130711093630.GL91021@kib.kiev.ua> References: <CAJ-Vmo=icr6bda%2BWMNUarc3WbdqJ%2BMdauX6kByxxdTx8oSovBg@mail.gmail.com> <20130711061753.GK91021@kib.kiev.ua> <CAJ-VmomFcZv6_uhpy6ShBzL21=Fqw7_y2xE2oYGod2T=Z5Qgpg@mail.gmail.com> <20130711093630.GL91021@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 July 2013 02:36, Konstantin Belousov <kostikbel@gmail.com> wrote: > No, it is not disk I/O which is problematic there. It is socket I/O > e.g. wait for the socket buffers lomark in the kern_sendfile() which > causes unbounded sleep. Look for the sbwait() call, both in the > kern_sendfile() itself, and in the pru_send methods of the protocols, > e.g. in sosend_generic(). The wait scope controlled by the other side of > connection and allow it to completely block the aio subsystem. > > Disk I/O is supposed to finish in the finite time. Even if the destination socket is marked as NONBLOCK? -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=ic_KuaaE2avvbX3JE=R25nuRyyAQpEmFrZRp7T9y9qg>