From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org
Cc: Leonardo Bras <leobras@redhat.com>,
qemu-block@nongnu.org, Fam Zheng <fam@euphon.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
Fabiano Rosas <farosas@suse.de>, Eric Blake <eblake@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH 5/6] nbd/server: only traverse NBDExport->clients from main loop thread
Date: Thu, 21 Dec 2023 08:23:15 +0100 [thread overview]
Message-ID: <8ff9a950-4075-4c86-bf5d-df8b90eb450a@redhat.com> (raw)
In-Reply-To: <20231221014903.1537962-6-stefanha@redhat.com>
On 12/21/23 02:49, Stefan Hajnoczi wrote:
> The NBD clients list is currently accessed from both the export
> AioContext and the main loop thread. When the AioContext lock is removed
> there will be nothing protecting the clients list.
>
> Adding a lock around the clients list is tricky because NBDClient
> structs are refcounted and may be freed from the export AioContext or
> the main loop thread. nbd_export_request_shutdown() -> client_close() ->
> nbd_client_put() is also tricky because the list lock would be held
> while indirectly dropping references to NDBClients.
>
> A simpler approach is to only allow nbd_client_put() and client_close()
> calls from the main loop thread. Then the NBD clients list is only
> accessed from the main loop thread and no fancy locking is needed.
>
> nbd_trip() just needs to reschedule itself in the main loop AioContext
> before calling nbd_client_put() and client_close(). This costs more CPU
> cycles per NBD request but is needed for thread-safety when the
> AioContext lock is removed.
>
> Note that nbd_client_get() can still be called from either thread, so
> make NBDClient->refcount atomic.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> nbd/server.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/nbd/server.c b/nbd/server.c
> index 0b09ccc8dc..527fbdab4a 100644
> --- a/nbd/server.c
> +++ b/nbd/server.c
> @@ -122,7 +122,7 @@ struct NBDMetaContexts {
> };
>
> struct NBDClient {
> - int refcount;
> + int refcount; /* atomic */
> void (*close_fn)(NBDClient *client, bool negotiated);
>
> NBDExport *exp;
> @@ -1501,14 +1501,17 @@ static int coroutine_fn nbd_receive_request(NBDClient *client, NBDRequest *reque
>
> #define MAX_NBD_REQUESTS 16
>
> +/* Runs in export AioContext and main loop thread */
> void nbd_client_get(NBDClient *client)
> {
> - client->refcount++;
> + qatomic_inc(&client->refcount);
> }
>
> void nbd_client_put(NBDClient *client)
> {
> - if (--client->refcount == 0) {
> + assert(qemu_in_main_thread());
> +
> + if (qatomic_fetch_dec(&client->refcount) == 1) {
> /* The last reference should be dropped by client->close,
> * which is called by client_close.
> */
> @@ -1531,6 +1534,8 @@ void nbd_client_put(NBDClient *client)
>
> static void client_close(NBDClient *client, bool negotiated)
> {
> + assert(qemu_in_main_thread());
> +
> if (client->closing) {
> return;
> }
> @@ -2938,8 +2943,15 @@ static coroutine_fn void nbd_trip(void *opaque)
> int ret;
> Error *local_err = NULL;
>
> + /*
> + * Note that nbd_client_put() and client_close() must be called from the
> + * main loop thread. Use aio_co_reschedule_self() to switch AioContext
> + * before calling these functions.
> + */
> +
> trace_nbd_trip();
> if (client->closing) {
> + aio_co_reschedule_self(qemu_get_aio_context());
> nbd_client_put(client);
> return;
> }
> @@ -2949,6 +2961,7 @@ static coroutine_fn void nbd_trip(void *opaque)
> * We're switching between AIO contexts. Don't attempt to receive a new
> * request and kick the main context which may be waiting for us.
> */
> + aio_co_reschedule_self(qemu_get_aio_context());
> nbd_client_put(client);
> client->recv_coroutine = NULL;
> aio_wait_kick();
> @@ -3013,6 +3026,8 @@ static coroutine_fn void nbd_trip(void *opaque)
> qio_channel_set_cork(client->ioc, false);
> done:
> nbd_request_put(req);
> +
> + aio_co_reschedule_self(qemu_get_aio_context());
> nbd_client_put(client);
> return;
This is very expensive to do on every NBD receive, considering that it really
can happen only when closing (see the assertion in nbd_client_put).
In Linux there is a common pattern of "if refcount could go to zero, take
a lock before doing the decrement". We can do something similar with "if
refcount could go to zero, move to main iothread before doing the decrement":
diff --git a/nbd/server.c b/nbd/server.c
index 895cf0a7525..aec306923d8 100644
--- a/nbd/server.c
+++ b/nbd/server.c
@@ -1529,6 +1529,21 @@ void nbd_client_put(NBDClient *client)
}
}
+static bool nbd_client_put_nonzero(NBDClient *client)
+{
+ int old = qatomic_read(&client->refcount);
+ do {
+ if (old == 1) {
+ return false;
+ }
+
+ int expected = old;
+ old = qatomic_cmpxchg(&client->refcount, expected, expected - 1);
+ } while (old != expected);
+
+ return true;
+}
+
static void client_close(NBDClient *client, bool negotiated)
{
if (client->closing) {
@@ -2936,15 +2951,14 @@ static coroutine_fn int nbd_handle_request(NBDClient *client,
static coroutine_fn void nbd_trip(void *opaque)
{
NBDClient *client = opaque;
- NBDRequestData *req;
+ NBDRequestData *req = NULL;
NBDRequest request = { 0 }; /* GCC thinks it can be used uninitialized */
int ret;
Error *local_err = NULL;
trace_nbd_trip();
if (client->closing) {
- nbd_client_put(client);
- return;
+ goto done;
}
if (client->quiescing) {
@@ -2952,10 +2966,9 @@ static coroutine_fn void nbd_trip(void *opaque)
* We're switching between AIO contexts. Don't attempt to receive a new
* request and kick the main context which may be waiting for us.
*/
- nbd_client_put(client);
client->recv_coroutine = NULL;
aio_wait_kick();
- return;
+ goto done;
}
req = nbd_request_get(client);
@@ -3015,8 +3028,13 @@ static coroutine_fn void nbd_trip(void *opaque)
qio_channel_set_cork(client->ioc, false);
done:
- nbd_request_put(req);
- nbd_client_put(client);
+ if (req) {
+ nbd_request_put(req);
+ }
+ if (!nbd_client_put_nonzero(client)) {
+ aio_co_reschedule_self(qemu_get_aio_context());
+ nbd_client_put(client);
+ }
return;
disconnect:
I think adding the "if (req)" should also simplify a little bit the addition of the lock.
Paolo
next prev parent reply other threads:[~2023-12-21 7:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 1:48 [PATCH 0/6] qemu-iotests fixes for Kevin's block tree Stefan Hajnoczi
2023-12-21 1:48 ` [PATCH 1/6] fixup block-coroutine-wrapper: use qemu_get_current_aio_context() Stefan Hajnoczi
2023-12-21 1:48 ` [PATCH 2/6] fixup block: remove AioContext locking Stefan Hajnoczi
2023-12-21 1:49 ` [PATCH 3/6] fixup scsi: only access SCSIDevice->requests from one thread Stefan Hajnoczi
2023-12-21 7:29 ` Paolo Bonzini
2023-12-21 1:49 ` [PATCH 4/6] nbd/server: avoid per-NBDRequest nbd_client_get/put() Stefan Hajnoczi
2023-12-21 7:27 ` Paolo Bonzini
2023-12-21 1:49 ` [PATCH 5/6] nbd/server: only traverse NBDExport->clients from main loop thread Stefan Hajnoczi
2023-12-21 7:23 ` Paolo Bonzini [this message]
2023-12-21 14:27 ` Stefan Hajnoczi
2024-01-02 15:32 ` Eric Blake
2023-12-21 1:49 ` [PATCH 6/6] nbd/server: introduce NBDClient->lock to protect fields Stefan Hajnoczi
2023-12-21 7:26 ` Paolo Bonzini
2023-12-21 11:56 ` Stefan Hajnoczi
2023-12-21 10:45 ` Kevin Wolf
2023-12-21 14:14 ` Stefan Hajnoczi
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=8ff9a950-4075-4c86-bf5d-df8b90eb450a@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--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).