From 0ab83370cb8e70a4440589051f14d99ae8cec588 Mon Sep 17 00:00:00 2001 From: Max Romanov Date: Tue, 5 Mar 2019 15:38:49 +0300 Subject: Handling ENOBUFS error same was as EAGAIN. Unlike EAGAIN, ENOBUFS returned on OSX when trying to send many relatively small (64 bytes) fragments. Found during investigation of #167 issue on GitHub. --- src/nxt_socketpair.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'src/nxt_socketpair.c') diff --git a/src/nxt_socketpair.c b/src/nxt_socketpair.c index a7396b31..0adbe1f6 100644 --- a/src/nxt_socketpair.c +++ b/src/nxt_socketpair.c @@ -94,9 +94,14 @@ nxt_socketpair_send(nxt_fd_event_t *ev, nxt_fd_t fd, nxt_iobuf_t *iob, case NXT_EAGAIN: nxt_debug(ev->task, "sendmsg(%d) not ready", ev->fd); - ev->write_ready = 0; + break; - return NXT_AGAIN; + /* + * Returned (at least on OSX) when trying to send many small messages. + */ + case NXT_ENOBUFS: + nxt_debug(ev->task, "sendmsg(%d) no buffers", ev->fd); + break; case NXT_EINTR: nxt_debug(ev->task, "sendmsg(%d) interrupted", ev->fd); @@ -108,6 +113,10 @@ nxt_socketpair_send(nxt_fd_event_t *ev, nxt_fd_t fd, nxt_iobuf_t *iob, return NXT_ERROR; } + + ev->write_ready = 0; + + return NXT_AGAIN; } } -- cgit