From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org, sagi@grimberg.me, hch@lst.de,
axboe@kernel.dk
Subject: Re: [PATCH RFC] nvme-tcp: allow multiple queues per hctx
Date: Tue, 6 Oct 2026 13:03:04 +0200 [thread overview]
Message-ID: <asTVaAMaOen5D395@kbusch-mbp> (raw)
In-Reply-To: <arFphFDlyHpnCv0J@kbusch-mbp>
On Mon, Sep 21, 2026 at 11:29:40AM -0600, Keith Busch wrote:
> I'm still trying to see if we can achieve a similar result just by
> making duplicate connections and letting the multipath policy handle the
> spread. That does improve things significantly, but I'm getting worse
> performance than this RFC, and I still don't know why yet.
Best I can tell, the duplicate multipath connections does what's desired
on the host side, but the target side (standard Linux in-kernel target)
ends up queueing all its work on the same CPU, so that appears to be why
my RFC is showing better performance.
prev parent reply other threads:[~2026-10-06 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 15:26 [PATCH RFC] nvme-tcp: allow multiple queues per hctx Keith Busch
2026-09-06 0:04 ` Sagi Grimberg
2026-09-08 14:21 ` Keith Busch
2026-09-08 17:10 ` Keith Busch
2026-09-09 5:21 ` Saravanan D
2026-09-11 21:44 ` Sagi Grimberg
2026-09-21 12:21 ` Hannes Reinecke
2026-09-21 17:29 ` Keith Busch
2026-10-06 11:03 ` Keith Busch [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=asTVaAMaOen5D395@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox