From: Joanne Koong <joannelkoong@gmail.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] fuse: {io-uring} Add queue length counters
Date: Thu, 24 Jul 2025 14:07:31 -0700 [thread overview]
Message-ID: <CAJnrk1Y82CRHeO6htyJsdsGEuJj6es9B=hg9CdK+bOuhc74AqQ@mail.gmail.com> (raw)
In-Reply-To: <20250722-reduced-nr-ring-queues_3-v1-1-aa8e37ae97e6@ddn.com>
On Tue, Jul 22, 2025 at 2:58 PM Bernd Schubert <bschubert@ddn.com> wrote:
>
> This is another preparation and will be used for decision
> which queue to add a request to.
> ---
> fs/fuse/dev_uring.c | 17 +++++++++++++++--
> fs/fuse/dev_uring_i.h | 3 +++
> 2 files changed, 18 insertions(+), 2 deletions(-)
LGTM
Reviewed-by: Joanne Koong <joannelkoong@gmail.com>
>
> diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
> index 249b210becb1cc2b40ae7b2fdf3a57dc57eaac42..2f2f7ff5e95a63a4df76f484d30cce1077b29123 100644
> --- a/fs/fuse/dev_uring.c
> +++ b/fs/fuse/dev_uring.c
next prev parent reply other threads:[~2025-07-24 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 21:57 [PATCH 0/5] fuse: {io-uring} Allow to reduce the number of queues and request distribution Bernd Schubert
2025-07-22 21:57 ` [PATCH 1/5] fuse: {io-uring} Add queue length counters Bernd Schubert
2025-07-24 21:07 ` Joanne Koong [this message]
2025-07-22 21:57 ` [PATCH 2/5] fuse: {io-uring} Rename ring->nr_queues to max_nr_queues Bernd Schubert
2025-07-22 21:58 ` [PATCH 3/5] fuse: {io-uring} Use bitmaps to track queue availability Bernd Schubert
2025-07-24 23:56 ` Joanne Koong
2025-07-22 21:58 ` [PATCH 4/5] fuse: {io-uring} Distribute load among queues Bernd Schubert
2025-07-22 21:58 ` [PATCH 5/5] fuse: {io-uring} Allow reduced number of ring queues Bernd Schubert
2025-07-25 0:43 ` Joanne Koong
2025-08-04 10:17 ` Bernd Schubert
2025-09-15 22:18 ` Bernd Schubert
2025-09-15 4:37 ` yangerkun
2025-09-15 8:39 ` Bernd Schubert
2025-09-15 9:07 ` yangerkun
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='CAJnrk1Y82CRHeO6htyJsdsGEuJj6es9B=hg9CdK+bOuhc74AqQ@mail.gmail.com' \
--to=joannelkoong@gmail.com \
--cc=bschubert@ddn.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).