linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd@bsbernd.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: miklos@szeredi.hu, axboe@kernel.dk,
	linux-fsdevel@vger.kernel.org, bschubert@ddn.com,
	asml.silence@gmail.com, io-uring@vger.kernel.org,
	xiaobing.li@samsung.com, csander@purestorage.com,
	kernel-team@meta.com
Subject: Re: [PATCH v2 5/8] fuse: use enum types for header copying
Date: Fri, 7 Nov 2025 23:11:55 +0100	[thread overview]
Message-ID: <505ab86f-bf13-41b9-8ccc-6e5cb83ef1b8@bsbernd.com> (raw)
In-Reply-To: <CAJnrk1apBiPMrDZDyVfLeFKLPdPiB=4e1d7D3QHsX5_6ZtFccA@mail.gmail.com>



On 11/6/25 22:59, Joanne Koong wrote:
> On Wed, Nov 5, 2025 at 3:01 PM Bernd Schubert <bernd@bsbernd.com> wrote:
>>
>> On 10/27/25 23:28, Joanne Koong wrote:
>>> Use enum types to identify which part of the header needs to be copied.
>>> This improves the interface and will simplify both kernel-space and
>>> user-space header addresses when fixed buffer support is added.
>>>
>>> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
>>> ---
>>>  fs/fuse/dev_uring.c | 55 ++++++++++++++++++++++++++++++++++++---------
>>>  1 file changed, 45 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
>>> index faa7217e85c4..d96368e93e8d 100644
>>> --- a/fs/fuse/dev_uring.c
>>> +++ b/fs/fuse/dev_uring.c
>>> @@ -31,6 +31,12 @@ struct fuse_uring_pdu {
>>>
>>>  static const struct fuse_iqueue_ops fuse_io_uring_ops;
>>>
>>> +enum fuse_uring_header_type {
>>> +     FUSE_URING_HEADER_IN_OUT,
>>
>> In post review of my own names, headers->in_out is rather hard to
>> understand, I would have probably chosen "msg_in_out" now.
>> With that _maybe_ FUSE_URING_HEADER_MSG_IN_OUT?
> 
> Ahh I personally find "msg" a bit more confusing because "message"
> makes me think it refers just to the payload since the whole thing is
> usually called the request. So if we had to rename it, maybe
> FUSE_URING_HEADER_REQ_IN_OUT? Though I do like your original naming of
> it, FUSE_URING_HEADER_IN_OUT since FUSE_URING_FUSE_HEADER_IN_OUT
> sounds a little redundant.

FUSE_URING_HEADER_REQ_IN_OUT sounds nice to me. Renaming was just a
suggestion. Let's keep the current name if you prefer that.

> 
> I'll add some comments on top of this too, eg "/*struct fuse_in_header
> / struct_fuse_out_header */, to clarify.

Comments are always helpful :)

> 
>>
>>> +     FUSE_URING_HEADER_OP,
>>> +     FUSE_URING_HEADER_RING_ENT,
>>> +};
>>> @@ -800,7 +835,7 @@ static void fuse_uring_commit(struct fuse_ring_ent *ent, struct fuse_req *req,
>>>       struct fuse_conn *fc = ring->fc;
>>>       ssize_t err = 0;
>>>
>>> -     err = copy_header_from_ring(&req->out.h, &ent->headers->in_out,
>>> +     err = copy_header_from_ring(ent, FUSE_URING_HEADER_IN_OUT, &req->out.h,
>>>                                   sizeof(req->out.h));
>>>       if (err) {
>>>               req->out.h.error = err;
>>
>>
>> Reviewed-by: Bernd Schubert <bschubert@ddn.com>
> 
> Thanks for reviewing the patches!
> 


  reply	other threads:[~2025-11-07 22:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 22:27 [PATCH v2 0/8] fuse: support io-uring registered buffers Joanne Koong
2025-10-27 22:28 ` [PATCH v2 1/8] io_uring/uring_cmd: add io_uring_cmd_import_fixed_full() Joanne Koong
2025-10-28  1:28   ` Caleb Sander Mateos
2025-10-29 14:01   ` Pavel Begunkov
2025-10-29 18:37     ` Joanne Koong
2025-10-29 19:59       ` Bernd Schubert
2025-10-30 17:42         ` Pavel Begunkov
2025-10-30 18:06       ` Pavel Begunkov
2025-10-30 22:23         ` Bernd Schubert
2025-10-30 23:50           ` Joanne Koong
2025-10-31 10:27             ` Bernd Schubert
2025-10-31 21:19               ` Joanne Koong
2025-10-30 23:13         ` Joanne Koong
2025-10-27 22:28 ` [PATCH v2 2/8] fuse: refactor io-uring logic for getting next fuse request Joanne Koong
2025-10-30 23:07   ` Bernd Schubert
2025-10-27 22:28 ` [PATCH v2 3/8] fuse: refactor io-uring header copying to ring Joanne Koong
2025-10-30 23:15   ` Bernd Schubert
2025-10-30 23:52     ` Joanne Koong
2025-10-27 22:28 ` [PATCH v2 4/8] fuse: refactor io-uring header copying from ring Joanne Koong
2025-10-27 22:28 ` [PATCH v2 5/8] fuse: use enum types for header copying Joanne Koong
2025-11-05 23:01   ` Bernd Schubert
2025-11-06 21:59     ` Joanne Koong
2025-11-07 22:11       ` Bernd Schubert [this message]
2025-10-27 22:28 ` [PATCH v2 6/8] fuse: add user_ prefix to userspace headers and payload fields Joanne Koong
2025-10-28  1:32   ` Caleb Sander Mateos
2025-10-28 23:56     ` Joanne Koong
2025-11-06 13:35   ` Bernd Schubert
2025-10-27 22:28 ` [PATCH v2 7/8] fuse: refactor setting up copy state for payload copying Joanne Koong
2025-11-06 16:53   ` Bernd Schubert
2025-11-06 22:01     ` Joanne Koong
2025-10-27 22:28 ` [PATCH v2 8/8] fuse: support io-uring registered buffers Joanne Koong
2025-10-28  1:42   ` Caleb Sander Mateos
2025-10-28 23:56     ` Joanne Koong
2025-11-06 19:48   ` Bernd Schubert
2025-11-06 23:09     ` Joanne Koong
2025-11-07 22:16       ` Bernd Schubert
2025-11-07 22:23         ` Bernd Schubert

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=505ab86f-bf13-41b9-8ccc-6e5cb83ef1b8@bsbernd.com \
    --to=bernd@bsbernd.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bschubert@ddn.com \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=joannelkoong@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=xiaobing.li@samsung.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).