From: Kevin Wolf <kwolf@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: qemu-block@nongnu.org, eblake@redhat.com,
vsementsov@yandex-team.ru, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] nbd/server: push pending frames after sending reply
Date: Fri, 24 Mar 2023 18:20:34 +0100 [thread overview]
Message-ID: <ZB3b4gw6FZHWvNz9@redhat.com> (raw)
In-Reply-To: <20230324104720.2498-1-fw@strlen.de>
Am 24.03.2023 um 11:47 hat Florian Westphal geschrieben:
> qemu-nbd doesn't set TCP_NODELAY on the tcp socket.
>
> Kernel waits for more data and avoids transmission of small packets.
> Without TLS this is barely noticeable, but with TLS this really shows.
>
> Booting a VM via qemu-nbd on localhost (with tls) takes more than
> 2 minutes on my system. tcpdump shows frequent wait periods, where no
> packets get sent for a 40ms period.
>
> Add explicit (un)corking when processing (and responding to) requests.
> "TCP_CORK, &zero" after earlier "CORK, &one" will flush pending data.
>
> VM Boot time:
> main: no tls: 23s, with tls: 2m45s
> patched: no tls: 14s, with tls: 15s
>
> VM Boot time, qemu-nbd via network (same lan):
> main: no tls: 18s, with tls: 1m50s
> patched: no tls: 17s, with tls: 18s
>
> Future optimization: if we could detect if there is another pending
> request we could defer the uncork operation because more data would be
> appended.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> nbd/server.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/nbd/server.c b/nbd/server.c
> index a4750e41880a..848836d41405 100644
> --- a/nbd/server.c
> +++ b/nbd/server.c
> @@ -2667,6 +2667,8 @@ static coroutine_fn void nbd_trip(void *opaque)
> goto disconnect;
> }
>
> + qio_channel_set_cork(client->ioc, true);
> +
> if (ret < 0) {
> /* It wasn't -EIO, so, according to nbd_co_receive_request()
> * semantics, we should return the error to the client. */
> @@ -2692,6 +2694,7 @@ static coroutine_fn void nbd_trip(void *opaque)
> goto disconnect;
> }
>
> + qio_channel_set_cork(client->ioc, false);
> done:
> nbd_request_put(req);
> nbd_client_put(client);
In the error paths, we never call set_cork(false) again. I suppose the
reason that this is okay is because the next thing is actually that we
close the socket?
Kevin
next prev parent reply other threads:[~2023-03-24 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:47 [PATCH 1/1] nbd/server: push pending frames after sending reply Florian Westphal
2023-03-24 17:20 ` Kevin Wolf [this message]
2023-03-24 18:20 ` Florian Westphal
2023-03-24 19:43 ` Eric Blake
2023-03-24 19:41 ` Eric Blake
2023-03-24 20:03 ` [Libguestfs] " Eric Blake
2023-03-24 23:55 ` Florian Westphal
2023-03-27 11:44 ` Kevin Wolf
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=ZB3b4gw6FZHWvNz9@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=fw@strlen.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).