From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
qemu-block@nongnu.org, "Michael Roth" <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/5] socket: Add num connections to qio_net_listener_open_sync()
Date: Wed, 4 Sep 2019 14:57:14 +0100 [thread overview]
Message-ID: <20190904135714.GB24521@redhat.com> (raw)
In-Reply-To: <87blw0kxly.fsf@trasno.org>
On Wed, Sep 04, 2019 at 03:19:21PM +0200, Juan Quintela wrote:
> Eric Blake <eblake@redhat.com> wrote:
> > On 8/20/19 5:48 AM, Juan Quintela wrote:
> >> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >> Signed-off-by: Juan Quintela <quintela@redhat.com>
> >> ---
> >> blockdev-nbd.c | 2 +-
> >> chardev/char-socket.c | 2 +-
> >> include/io/net-listener.h | 2 ++
> >> io/net-listener.c | 3 ++-
> >> migration/socket.c | 2 +-
> >> qemu-nbd.c | 2 +-
> >> ui/vnc.c | 4 ++--
> >> 7 files changed, 10 insertions(+), 7 deletions(-)
> >
> > Just now noticing this one, even though the pull request is already sent...
> >
> >>
> >> diff --git a/blockdev-nbd.c b/blockdev-nbd.c
> >> index 7a71da447f..c621686131 100644
> >> --- a/blockdev-nbd.c
> >> +++ b/blockdev-nbd.c
> >> @@ -101,7 +101,7 @@ 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, errp) < 0) {
> >> + if (qio_net_listener_open_sync(nbd_server->listener, addr, 1, errp) < 0) {
> >> goto error;
> >> }
> >
> > Does this interfere with the ability to have more than one client
> > connect to an NBD server during pull-mode incremental backup? Or can
> > you still have multiple simultaneous clients, provided that the server
> > has finished accepting the connection from the first before the second
> > one starts?
>
> It is exactly the same than the old code. Old code always use one. We
> need to have more than one for multifd.
>
> Once told that, if the connections don't start "very" simultaneosly
> (i..e. With multifd we start <num channels> connections in paraller),
> you will never notice that the backlog is one (sie of queue of pending
> connections nowadays).
If incremental backup needs multiple concurrent connections, then
you certainly *do* want to increase this value to something other
than 1, or you will get random failures. As Juan says, this is a
pre-existing problem with NBD though.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-09-04 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 10:48 [Qemu-devel] [PATCH v3 0/5] Fix multifd with big number of channels Juan Quintela
2019-08-20 10:48 ` [Qemu-devel] [PATCH v3 1/5] socket: Add backlog parameter to socket_listen Juan Quintela
2019-08-20 10:50 ` Daniel P. Berrangé
2019-08-20 11:17 ` Juan Quintela
2019-08-22 14:19 ` Daniel P. Berrangé
2019-08-20 10:48 ` [Qemu-devel] [PATCH v3 2/5] socket: Add num connections to qio_channel_socket_sync() Juan Quintela
2019-08-20 10:48 ` [Qemu-devel] [PATCH v3 3/5] socket: Add num connections to qio_channel_socket_async() Juan Quintela
2019-08-20 10:48 ` [Qemu-devel] [PATCH v3 4/5] socket: Add num connections to qio_net_listener_open_sync() Juan Quintela
2019-09-04 12:39 ` Eric Blake
2019-09-04 13:19 ` Juan Quintela
2019-09-04 13:57 ` Daniel P. Berrangé [this message]
2019-08-20 10:48 ` [Qemu-devel] [PATCH v3 5/5] multifd: Use number of channels as listen backlog Juan Quintela
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=20190904135714.GB24521@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=fam@euphon.net \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanb@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).