From: Keith Busch <kbusch@kernel.org>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: linux-nvme@lists.infradead.org
Subject: Re: Number of data and admin queues in use
Date: Tue, 15 Jul 2025 08:39:00 -0600 [thread overview]
Message-ID: <aHZoBO9cPcRGIDwH@kbusch-mbp> (raw)
In-Reply-To: <aHW1qUJksE5Okflb@glanzmann.de>
On Tue, Jul 15, 2025 at 03:58:01AM +0200, Thomas Glanzmann wrote:
> I one heard that the Linux kernel allocates one queue per processor (core or
> hyperthread). I can see that using /proc/interrupts but only on physical
> devices, but not on NVME/TCP systems.
For PCI, the driver automatically handles the queue and interrupt setup,
and cpu assignment.
For TCP (and all fabrics transports), you have to specificy how many
connections you want to make ("nr_io_queues=X") when you're setting up
your initial fabrics connection.
If you want to see what you've ended up with, you can consult the
namespaces' sysfs entries:
How many IO queues are there:
# ls -1 /sys/block/nvme0n1/mq/ | wc -l
64
How large is each IO queue:
# cat /sys/block/nvme0n1/queue/nr_requests
1023
next prev parent reply other threads:[~2025-07-15 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 1:58 Number of data and admin queues in use Thomas Glanzmann
2025-07-15 14:39 ` Keith Busch [this message]
2025-07-15 16:38 ` Thomas Glanzmann
2025-07-15 17:22 ` Chaitanya Kulkarni
2025-07-15 18:05 ` Thomas Glanzmann
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=aHZoBO9cPcRGIDwH@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=thomas@glanzmann.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.