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 4/6] nbd/server: avoid per-NBDRequest nbd_client_get/put()
Date: Thu, 21 Dec 2023 08:27:09 +0100 [thread overview]
Message-ID: <913d0d34-a1ce-4bf3-9ed2-e194cbae1a78@redhat.com> (raw)
In-Reply-To: <20231221014903.1537962-5-stefanha@redhat.com>
On 12/21/23 02:49, Stefan Hajnoczi wrote:
> nbd_trip() processes a single NBD request from start to finish and holds
> an NBDClient reference throughout. NBDRequest does not outlive the scope
> of nbd_trip(). Therefore it is unnecessary to ref/unref NBDClient for
> each NBDRequest.
>
> Removing these nbd_client_get()/nbd_client_put() calls will make
> thread-safety easier in the commits that follow.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> nbd/server.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/nbd/server.c b/nbd/server.c
> index 895cf0a752..0b09ccc8dc 100644
> --- a/nbd/server.c
> +++ b/nbd/server.c
> @@ -1557,7 +1557,6 @@ static NBDRequestData *nbd_request_get(NBDClient *client)
> client->nb_requests++;
>
> req = g_new0(NBDRequestData, 1);
> - nbd_client_get(client);
> req->client = client;
> return req;
> }
> @@ -1578,8 +1577,6 @@ static void nbd_request_put(NBDRequestData *req)
> }
>
> nbd_client_receive_next_request(client);
> -
> - nbd_client_put(client);
> }
>
> static void blk_aio_attached(AioContext *ctx, void *opaque)
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2023-12-21 7:27 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 [this message]
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
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=913d0d34-a1ce-4bf3-9ed2-e194cbae1a78@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).