From: Nilay Shroff <nilay@linux.ibm.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, hare@suse.de, kbusch@kernel.org,
hch@lst.de, gjoyce@linux.ibm.com, chaitanyak@nvidia.com
Subject: Re: [PATCH 0/3] nvme-cli: NIC topology aware I/O queue scaling
Date: Fri, 9 Oct 2026 15:01:38 +0530 [thread overview]
Message-ID: <e164ee63-41e1-41cc-9b10-d7cb44a9b3ed@linux.ibm.com> (raw)
In-Reply-To: <11d3490e-f8ce-4559-b1d3-f115f7dbced2@flourine.local>
On 10/6/26 12:08 PM, Daniel Wagner wrote:
> Hi Nilay,
>
> On Sat, Sep 12, 2026 at 05:41:07PM +0530, Nilay Shroff wrote:
>>> This would preserve the existing behavior for single-queue devices while still using the
>>> NIC hardware queue count to constrain the default on multi-queue devices.
>>>
>>> Does this look reasonable?
>
> Could you rebase and send also a PR on github. I'd like to run the
> review bot on this.
Yes, I have pushed this PR: https://github.com/linux-nvme/nvme-cli/pull/4140
Thanks,
--Nilay
prev parent reply other threads:[~2026-10-09 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 14:43 [PATCH 0/3] nvme-cli: NIC topology aware I/O queue scaling Nilay Shroff
2026-08-21 14:43 ` [PATCH 1/3] shared/net-util-linux: add support for retrieving egress netdev Nilay Shroff
2026-08-21 14:43 ` [PATCH 2/3] shared/net-util-linux: add support for retrieving NIC h/w queues Nilay Shroff
2026-08-21 14:43 ` [PATCH 3/3] fabrics: determine --nr-io-queues when not explicitly specified Nilay Shroff
2026-08-22 21:43 ` [PATCH 0/3] nvme-cli: NIC topology aware I/O queue scaling Sagi Grimberg
2026-08-24 8:48 ` Nilay Shroff
2026-08-30 22:06 ` Sagi Grimberg
2026-08-31 5:04 ` Nilay Shroff
2026-09-09 9:08 ` Daniel Wagner
2026-09-09 9:28 ` Nilay Shroff
2026-09-12 12:11 ` Nilay Shroff
2026-10-06 6:38 ` Daniel Wagner
2026-10-09 9:31 ` Nilay Shroff [this message]
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=e164ee63-41e1-41cc-9b10-d7cb44a9b3ed@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=gjoyce@linux.ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.