From: Joanne Koong <joannelkoong@gmail.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, Luis Henriques <luis@igalia.com>,
Gang He <dchg2000@gmail.com>
Subject: Re: [PATCH v3 3/6] fuse: {io-uring} Use bitmaps to track registered queues
Date: Wed, 15 Oct 2025 16:49:02 -0700 [thread overview]
Message-ID: <CAJnrk1aaVa4hc_VC4G1axT1_=b6eyRW01KVczhvitCcsN7cACw@mail.gmail.com> (raw)
In-Reply-To: <20251013-reduced-nr-ring-queues_3-v3-3-6d87c8aa31ae@ddn.com>
> @@ -983,6 +1031,10 @@ static void fuse_uring_do_register(struct fuse_ring_ent *ent,
> struct fuse_ring *ring = queue->ring;
> struct fuse_conn *fc = ring->fc;
> struct fuse_iqueue *fiq = &fc->iq;
> + int node = cpu_to_node(queue->qid);
Am I reading the correct version of the libfuse implementation in [1]?
As I understand it, the libfuse implementation sets queue->qid
sequentially no matter the user-specified cpu-set [2], but the qid is
used as the cpu id, and we get the numa node from that. My
understanding is that in practice, sequential CPU numbering often
follows NUMA topology (eg NUMA node0 cpus: 0-15, 32-47; NUMA node1
cpus: 16-31), so it seems like this has a high chance of being all on
the same numa node? Or am I missing something here?
Thanks,
Joanne
[1] https://github.com/bsbernd/libfuse/commit/afcc654c8760f0c95f9e042fc92f05b1b9c3df13
[2] https://github.com/bsbernd/libfuse/blob/afcc654c8760f0c95f9e042fc92f05b1b9c3df13/lib/fuse_uring.c#L830
> +
> + if (WARN_ON_ONCE(node >= ring->nr_numa_nodes))
> + node = 0;
>
> fuse_uring_prepare_cancel(cmd, issue_flags, ent);
>
> @@ -991,6 +1043,9 @@ static void fuse_uring_do_register(struct fuse_ring_ent *ent,
> fuse_uring_ent_avail(ent, queue);
> spin_unlock(&queue->lock);
>
> + cpumask_set_cpu(queue->qid, ring->registered_q_mask);
> + cpumask_set_cpu(queue->qid, ring->numa_registered_q_mask[node]);
> +
> if (!ring->ready) {
> bool ready = is_ring_ready(ring, queue->qid);
>
next prev parent reply other threads:[~2025-10-15 23:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 17:09 [PATCH v3 0/6] fuse: {io-uring} Allow to reduce the number of queues and request distribution Bernd Schubert
2025-10-13 17:09 ` [PATCH v3 1/6] fuse: {io-uring} Add queue length counters Bernd Schubert
2025-10-15 9:19 ` Luis Henriques
2025-10-13 17:09 ` [PATCH v3 2/6] fuse: {io-uring} Rename ring->nr_queues to max_nr_queues Bernd Schubert
2025-10-13 17:09 ` [PATCH v3 3/6] fuse: {io-uring} Use bitmaps to track registered queues Bernd Schubert
2025-10-15 23:49 ` Joanne Koong [this message]
2025-10-16 11:33 ` Bernd Schubert
2025-10-13 17:10 ` [PATCH v3 4/6] fuse: {io-uring} Distribute load among queues Bernd Schubert
2025-10-18 0:12 ` Joanne Koong
2025-10-20 19:00 ` Bernd Schubert
2025-10-20 22:59 ` Joanne Koong
2025-10-20 23:28 ` Bernd Schubert
2025-10-24 17:05 ` Joanne Koong
2025-10-24 17:52 ` Bernd Schubert
2025-10-24 17:58 ` Bernd Schubert
2025-10-13 17:10 ` [PATCH v3 5/6] fuse: {io-uring} Allow reduced number of ring queues Bernd Schubert
2025-10-15 9:25 ` Luis Henriques
2025-10-15 9:31 ` Bernd Schubert
2025-10-13 17:10 ` [PATCH v3 6/6] fuse: {io-uring} Queue background requests on a different core Bernd Schubert
2025-10-15 9:50 ` Luis Henriques
2025-10-15 10:27 ` Bernd Schubert
2025-10-15 11:05 ` Luis Henriques
2025-10-20 7:15 ` Dan Carpenter
2025-10-14 8:43 ` [PATCH v3 0/6] fuse: {io-uring} Allow to reduce the number of queues and request distribution Gang He
2025-10-14 9:14 ` Bernd Schubert
2025-10-16 6:15 ` Gang He
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='CAJnrk1aaVa4hc_VC4G1axT1_=b6eyRW01KVczhvitCcsN7cACw@mail.gmail.com' \
--to=joannelkoong@gmail.com \
--cc=bschubert@ddn.com \
--cc=dchg2000@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luis@igalia.com \
--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).