From: Bernd Schubert <bschubert@ddn.com>
To: Joanne Koong <joannelkoong@gmail.com>,
"miklos@szeredi.hu" <miklos@szeredi.hu>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"asml.silence@gmail.com" <asml.silence@gmail.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"xiaobing.li@samsung.com" <xiaobing.li@samsung.com>,
"csander@purestorage.com" <csander@purestorage.com>,
"kernel-team@meta.com" <kernel-team@meta.com>
Subject: Re: [PATCH v2 2/8] fuse: refactor io-uring logic for getting next fuse request
Date: Thu, 30 Oct 2025 23:07:46 +0000 [thread overview]
Message-ID: <481f7dc2-e6a3-4bfd-903a-9e3537f7a468@ddn.com> (raw)
In-Reply-To: <20251027222808.2332692-3-joannelkoong@gmail.com>
On 10/27/25 23:28, Joanne Koong wrote:
> Simplify the logic for getting the next fuse request.
>
> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
> ---
> fs/fuse/dev_uring.c | 78 ++++++++++++++++-----------------------------
> 1 file changed, 28 insertions(+), 50 deletions(-)
>
> diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
> index f6b12aebb8bb..415924b346c0 100644
> --- a/fs/fuse/dev_uring.c
> +++ b/fs/fuse/dev_uring.c
> @@ -710,34 +710,6 @@ static int fuse_uring_prepare_send(struct fuse_ring_ent *ent,
> return err;
> }
>
> -/*
> - * Write data to the ring buffer and send the request to userspace,
> - * userspace will read it
> - * This is comparable with classical read(/dev/fuse)
> - */
> -static int fuse_uring_send_next_to_ring(struct fuse_ring_ent *ent,
> - struct fuse_req *req,
> - unsigned int issue_flags)
> -{
> - struct fuse_ring_queue *queue = ent->queue;
> - int err;
> - struct io_uring_cmd *cmd;
> -
> - err = fuse_uring_prepare_send(ent, req);
> - if (err)
> - return err;
> -
> - spin_lock(&queue->lock);
> - cmd = ent->cmd;
> - ent->cmd = NULL;
> - ent->state = FRRS_USERSPACE;
> - list_move_tail(&ent->list, &queue->ent_in_userspace);
> - spin_unlock(&queue->lock);
> -
> - io_uring_cmd_done(cmd, 0, issue_flags);
> - return 0;
> -}
> -
> /*
> * Make a ring entry available for fuse_req assignment
> */
> @@ -834,11 +806,13 @@ static void fuse_uring_commit(struct fuse_ring_ent *ent, struct fuse_req *req,
> }
>
> /*
> - * Get the next fuse req and send it
> + * Get the next fuse req.
> + *
> + * Returns true if the next fuse request has been assigned to the ent.
> + * Else, there is no next fuse request and this returns false.
> */
> -static void fuse_uring_next_fuse_req(struct fuse_ring_ent *ent,
> - struct fuse_ring_queue *queue,
> - unsigned int issue_flags)
> +static bool fuse_uring_get_next_fuse_req(struct fuse_ring_ent *ent,
> + struct fuse_ring_queue *queue)
> {
> int err;
> struct fuse_req *req;
> @@ -850,10 +824,12 @@ static void fuse_uring_next_fuse_req(struct fuse_ring_ent *ent,
> spin_unlock(&queue->lock);
>
> if (req) {
> - err = fuse_uring_send_next_to_ring(ent, req, issue_flags);
> + err = fuse_uring_prepare_send(ent, req);
> if (err)
> goto retry;
> }
> +
> + return req != NULL;
> }
>
> static int fuse_ring_ent_set_commit(struct fuse_ring_ent *ent)
> @@ -871,6 +847,20 @@ static int fuse_ring_ent_set_commit(struct fuse_ring_ent *ent)
> return 0;
> }
>
> +static void fuse_uring_send(struct fuse_ring_ent *ent, struct io_uring_cmd *cmd,
> + ssize_t ret, unsigned int issue_flags)
> +{
> + struct fuse_ring_queue *queue = ent->queue;
> +
> + spin_lock(&queue->lock);
> + ent->state = FRRS_USERSPACE;
> + list_move_tail(&ent->list, &queue->ent_in_userspace);
> + ent->cmd = NULL;
> + spin_unlock(&queue->lock);
> +
> + io_uring_cmd_done(cmd, ret, issue_flags);
> +}
> +
> /* FUSE_URING_CMD_COMMIT_AND_FETCH handler */
> static int fuse_uring_commit_fetch(struct io_uring_cmd *cmd, int issue_flags,
> struct fuse_conn *fc)
> @@ -942,7 +932,8 @@ static int fuse_uring_commit_fetch(struct io_uring_cmd *cmd, int issue_flags,
> * and fetching is done in one step vs legacy fuse, which has separated
> * read (fetch request) and write (commit result).
> */
> - fuse_uring_next_fuse_req(ent, queue, issue_flags);
> + if (fuse_uring_get_next_fuse_req(ent, queue))
> + fuse_uring_send(ent, cmd, 0, issue_flags);
> return 0;
> }
>
> @@ -1190,20 +1181,6 @@ int fuse_uring_cmd(struct io_uring_cmd *cmd, unsigned int issue_flags)
> return -EIOCBQUEUED;
> }
>
> -static void fuse_uring_send(struct fuse_ring_ent *ent, struct io_uring_cmd *cmd,
> - ssize_t ret, unsigned int issue_flags)
> -{
> - struct fuse_ring_queue *queue = ent->queue;
> -
> - spin_lock(&queue->lock);
> - ent->state = FRRS_USERSPACE;
> - list_move_tail(&ent->list, &queue->ent_in_userspace);
> - ent->cmd = NULL;
> - spin_unlock(&queue->lock);
> -
> - io_uring_cmd_done(cmd, ret, issue_flags);
> -}
> -
> /*
> * This prepares and sends the ring request in fuse-uring task context.
> * User buffers are not mapped yet - the application does not have permission
> @@ -1219,8 +1196,9 @@ static void fuse_uring_send_in_task(struct io_uring_cmd *cmd,
> if (!(issue_flags & IO_URING_F_TASK_DEAD)) {
> err = fuse_uring_prepare_send(ent, ent->fuse_req);
> if (err) {
> - fuse_uring_next_fuse_req(ent, queue, issue_flags);
> - return;
> + if (!fuse_uring_get_next_fuse_req(ent, queue))
> + return;
> + err = 0;
> }
> } else {
> err = -ECANCELED;
LGTM
(I had already start to go into this direction
https://lore.kernel.org/all/20250403-fuse-io-uring-trace-points-v3-3-35340aa31d9c@ddn.com/)
Reviewed-by: Bernd Schubert <bschubert@ddn.com>
next prev parent reply other threads:[~2025-10-30 23:07 UTC|newest]
Thread overview: 40+ 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 [this message]
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
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
2025-11-23 20:12 ` Bernd Schubert
2025-11-25 1:13 ` Joanne Koong
2025-11-14 23:59 ` [PATCH v2 0/8] " Joanne Koong
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=481f7dc2-e6a3-4bfd-903a-9e3537f7a468@ddn.com \
--to=bschubert@ddn.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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