All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"open list:Network Block Dev..." <qemu-block@nongnu.org>,
	qemu-stable@nongnu.org,
	"Richard W . M . Jones" <rjones@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>
Subject: [PULL 01/14] qemu-nbd: Use SOMAXCONN for socket listen() backlog
Date: Fri, 12 Feb 2021 14:16:06 -0600	[thread overview]
Message-ID: <20210212201619.1388255-2-eblake@redhat.com> (raw)
In-Reply-To: <20210212201619.1388255-1-eblake@redhat.com>

Our default of a backlog of 1 connection is rather puny; it gets in
the way when we are explicitly allowing multiple clients (such as
qemu-nbd -e N [--shared], or nbd-server-start with its default
"max-connections":0 for unlimited), but is even a problem when we
stick to qemu-nbd's default of only 1 active client but use -t
[--persistent] where a second client can start using the server once
the first finishes.  While the effects are less noticeable on TCP
sockets (since the client can poll() to learn when the server is ready
again), it is definitely observable on Unix sockets, where on Linux, a
client will fail with EAGAIN and no recourse but to sleep an arbitrary
amount of time before retrying if the server backlog is already full.

Since QMP nbd-server-start is always persistent, it now always
requests a backlog of SOMAXCONN; meanwhile, qemu-nbd will request
SOMAXCONN if persistent, otherwise its backlog should be based on the
expected number of clients.

See https://bugzilla.redhat.com/1925045 for a demonstration of where
our low backlog prevents libnbd from connecting as many parallel
clients as it wants.

Reported-by: Richard W.M. Jones <rjones@redhat.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
CC: qemu-stable@nongnu.org
Message-Id: <20210209152759.209074-2-eblake@redhat.com>
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
---
 blockdev-nbd.c |  7 ++++++-
 qemu-nbd.c     | 10 +++++++++-
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/blockdev-nbd.c b/blockdev-nbd.c
index d8443d235b73..b264620b98d8 100644
--- a/blockdev-nbd.c
+++ b/blockdev-nbd.c
@@ -134,7 +134,12 @@ void nbd_server_start(SocketAddress *addr, const char *tls_creds,
     qio_net_listener_set_name(nbd_server->listener,
                               "nbd-listener");

-    if (qio_net_listener_open_sync(nbd_server->listener, addr, 1, errp) < 0) {
+    /*
+     * Because this server is persistent, a backlog of SOMAXCONN is
+     * better than trying to size it to max_connections.
+     */
+    if (qio_net_listener_open_sync(nbd_server->listener, addr, SOMAXCONN,
+                                   errp) < 0) {
         goto error;
     }

diff --git a/qemu-nbd.c b/qemu-nbd.c
index 608c63e82a25..1a340ea4858d 100644
--- a/qemu-nbd.c
+++ b/qemu-nbd.c
@@ -964,8 +964,16 @@ int main(int argc, char **argv)

     server = qio_net_listener_new();
     if (socket_activation == 0) {
+        int backlog;
+
+        if (persistent) {
+            backlog = SOMAXCONN;
+        } else {
+            backlog = MIN(shared, SOMAXCONN);
+        }
         saddr = nbd_build_socket_address(sockpath, bindto, port);
-        if (qio_net_listener_open_sync(server, saddr, 1, &local_err) < 0) {
+        if (qio_net_listener_open_sync(server, saddr, backlog,
+                                       &local_err) < 0) {
             object_unref(OBJECT(server));
             error_report_err(local_err);
             exit(EXIT_FAILURE);
-- 
2.30.1



  reply	other threads:[~2021-02-12 20:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 20:16 [PULL 00/14] NBD patches through 2021-02-12 Eric Blake
2021-02-12 20:16 ` Eric Blake [this message]
2021-02-12 20:16 ` [PULL 02/14] qemu-nbd: Permit --shared=0 for unlimited clients Eric Blake
2021-02-12 20:16 ` [PULL 03/14] iotests/210: Fix reference output Eric Blake
2021-02-12 20:16 ` [PULL 04/14] io: error_prepend() in qio_channel_readv_full_all() causes segfault Eric Blake
2021-02-12 20:16 ` [PULL 05/14] block: add new BlockDriver handler: bdrv_cancel_in_flight Eric Blake
2021-02-12 20:16 ` [PULL 06/14] block/nbd: implement .bdrv_cancel_in_flight Eric Blake
2021-02-12 20:16 ` [PULL 07/14] block/raw-format: implement .bdrv_cancel_in_flight handler Eric Blake
2021-02-12 20:16 ` [PULL 08/14] job: add .cancel handler for the driver Eric Blake
2021-02-12 20:16 ` [PULL 09/14] block/mirror: implement .cancel job handler Eric Blake
2021-02-12 20:16 ` [PULL 10/14] iotests/264: move to python unittest Eric Blake
2021-02-12 20:16 ` [PULL 11/14] iotests.py: qemu_nbd_popen: remove pid file after use Eric Blake
2021-02-12 20:16 ` [PULL 12/14] iotests/264: add mirror-cancel test-case Eric Blake
2021-02-12 20:16 ` [PULL 13/14] block/backup: implement .cancel job handler Eric Blake
2021-02-12 20:16 ` [PULL 14/14] iotests/264: add backup-cancel test-case Eric Blake
2021-02-13 18:16 ` [PULL 00/14] NBD patches through 2021-02-12 Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210212201619.1388255-2-eblake@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=rjones@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.