qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Kevin Wolf <kwolf@redhat.com>
Subject: Re: [PATCH 08/15] fuse: Introduce fuse_{at,de}tach_handlers()
Date: Fri, 4 Apr 2025 13:24:43 +0200	[thread overview]
Message-ID: <0cbc0080-cade-4018-b283-cdbb3b489da4@redhat.com> (raw)
In-Reply-To: <4r7vggv7jwq376focbc2mhad2b3cfs7eowsgge2ppwtd47c33u@cw3vd3tqxy3x>

On 01.04.25 15:55, Eric Blake wrote:
> On Tue, Mar 25, 2025 at 05:06:48PM +0100, Hanna Czenczek wrote:
>> Pull setting up and tearing down the AIO context handlers into two
>> dedicated functions.
>>
>> Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
>> ---
>>   block/export/fuse.c | 32 ++++++++++++++++----------------
>>   1 file changed, 16 insertions(+), 16 deletions(-)
>>
>> diff --git a/block/export/fuse.c b/block/export/fuse.c
>> index 2df6297d61..bd98809d71 100644
>> --- a/block/export/fuse.c
>> +++ b/block/export/fuse.c
>> @@ -78,27 +78,34 @@ static void read_from_fuse_export(void *opaque);
>>   static bool is_regular_file(const char *path, Error **errp);
>>   
>>   
>> -static void fuse_export_drained_begin(void *opaque)
>> +static void fuse_attach_handlers(FuseExport *exp)
>>   {
>> -    FuseExport *exp = opaque;
>> +    aio_set_fd_handler(exp->common.ctx,
>> +                       fuse_session_fd(exp->fuse_session),
>> +                       read_from_fuse_export, NULL, NULL, NULL, exp);
>> +    exp->fd_handler_set_up = true;
> I found this name mildly confusing (does "set_up=true" mean that I
> still need to set up, or that I am already set up);

Not my fault that English has irregular verbs.  FWIW, if I meant the 
former, I’d probably call it “set_up_fd_handler” instead.

> would it be better
> as s/fd_handler_set_up/fd_handler_armed/g ?

I prefer the less militaristic “installed”, but sure.

Hanna



  reply	other threads:[~2025-04-04 11:25 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 16:05 [PATCH 00/15] export/fuse: Use coroutines and multi-threading Hanna Czenczek
2025-03-25 16:06 ` [PATCH 01/15] fuse: Copy write buffer content before polling Hanna Czenczek
2025-03-27 14:47   ` Stefan Hajnoczi
2025-04-04 11:17     ` Hanna Czenczek
2025-04-01 13:44   ` Eric Blake
2025-04-04 11:18     ` Hanna Czenczek
2025-03-25 16:06 ` [PATCH 02/15] fuse: Ensure init clean-up even with error_fatal Hanna Czenczek
2025-03-26  5:47   ` Markus Armbruster
2025-03-26  9:49     ` Hanna Czenczek
2025-03-27 14:51   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 03/15] fuse: Remove superfluous empty line Hanna Czenczek
2025-03-27 14:53   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 04/15] fuse: Explicitly set inode ID to 1 Hanna Czenczek
2025-03-27 14:54   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 05/15] fuse: Change setup_... to mount_fuse_export() Hanna Czenczek
2025-03-27 14:55   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 06/15] fuse: Fix mount options Hanna Czenczek
2025-03-27 14:58   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 07/15] fuse: Set direct_io and parallel_direct_writes Hanna Czenczek
2025-03-27 15:09   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 08/15] fuse: Introduce fuse_{at,de}tach_handlers() Hanna Czenczek
2025-03-27 15:12   ` Stefan Hajnoczi
2025-04-01 13:55   ` Eric Blake
2025-04-04 11:24     ` Hanna Czenczek [this message]
2025-03-25 16:06 ` [PATCH 09/15] fuse: Introduce fuse_{inc,dec}_in_flight() Hanna Czenczek
2025-03-27 15:13   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 10/15] fuse: Add halted flag Hanna Czenczek
2025-03-27 15:15   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 11/15] fuse: Manually process requests (without libfuse) Hanna Czenczek
2025-03-27 15:35   ` Stefan Hajnoczi
2025-04-04 12:36     ` Hanna Czenczek
2025-04-01 14:35   ` Eric Blake
2025-04-04 11:30     ` Hanna Czenczek
2025-04-04 11:42     ` Hanna Czenczek
2025-03-25 16:06 ` [PATCH 12/15] fuse: Reduce max read size Hanna Czenczek
2025-03-27 15:35   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 13/15] fuse: Process requests in coroutines Hanna Czenczek
2025-03-27 15:38   ` Stefan Hajnoczi
2025-03-25 16:06 ` [PATCH 14/15] fuse: Implement multi-threading Hanna Czenczek
2025-03-26  5:38   ` Markus Armbruster
2025-03-26  9:55     ` Hanna Czenczek
2025-03-26 11:41       ` Markus Armbruster
2025-03-26 13:56         ` Hanna Czenczek
2025-03-27 12:18           ` Markus Armbruster via
2025-03-27 13:45             ` Hanna Czenczek
2025-04-01 12:05               ` Kevin Wolf
2025-04-01 20:31                 ` Eric Blake
2025-04-04 12:45                 ` Hanna Czenczek
2025-03-27 15:55   ` Stefan Hajnoczi
2025-04-01 20:36     ` Eric Blake
2025-04-02 13:20       ` Stefan Hajnoczi
2025-04-03 17:59         ` Eric Blake
2025-04-04 12:49     ` Hanna Czenczek
2025-04-07 14:02       ` Stefan Hajnoczi
2025-04-01 14:58   ` Eric Blake
2025-03-25 16:06 ` [PATCH 15/15] fuse: Increase MAX_WRITE_SIZE with a second buffer Hanna Czenczek
2025-03-27 15:59   ` Stefan Hajnoczi
2025-04-01 20:24   ` Eric Blake
2025-04-04 13:04     ` Hanna Czenczek

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=0cbc0080-cade-4018-b283-cdbb3b489da4@redhat.com \
    --to=hreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).