From: Keith Busch <kbusch@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: John Garry <john.g.garry@oracle.com>,
lsf-pc@lists.linux-foundation.org,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Native SCSI multipath support
Date: Tue, 17 Feb 2026 13:13:38 -0700 [thread overview]
Message-ID: <aZTL8srSowTU81Rz@kbusch-mbp> (raw)
In-Reply-To: <049a177d-85d6-4c9d-9a9a-f07391046101@acm.org>
On Tue, Feb 17, 2026 at 11:33:12AM -0800, Bart Van Assche wrote:
> More important: what will the performance impact be on SCSI devices that
> do not need multipath support? UFS devices don't need multipath support
> and soon (later this year) will support more than one million IOPS per
> device. Further performance improvements are on the roadmap.
For nvme, we can detect if a device is multipath capable. If not, we
skip the multipath layer altogether so it has no performance impact. I'd
imagine the generic library version would similarly require an opt-in
approach that UFS simply wouldn't subscribe to.
next prev parent reply other threads:[~2026-02-17 20:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 14:19 [LSF/MM/BPF TOPIC] Native SCSI multipath support John Garry
2026-02-13 17:21 ` Hannes Reinecke
2026-02-14 9:42 ` John Garry
2026-02-16 7:26 ` Hannes Reinecke
2026-02-16 16:32 ` Hannes Reinecke
2026-02-16 16:55 ` John Garry
2026-02-17 7:05 ` Hannes Reinecke
2026-02-21 17:47 ` Mike Snitzer
2026-02-17 19:33 ` Bart Van Assche
2026-02-17 20:13 ` Keith Busch [this message]
2026-02-18 2:39 ` [Lsf-pc] " Martin K. Petersen
2026-02-18 7:35 ` Hannes Reinecke
2026-02-18 8:35 ` John Garry
2026-02-18 8:23 ` John Garry
2026-02-21 17:41 ` Mike Snitzer
2026-02-24 9:56 ` John Garry
2026-02-25 0:46 ` Benjamin Marzinski
2026-02-25 8:11 ` Hannes Reinecke
2026-02-25 9:26 ` John Garry
2026-03-10 17:12 ` Ewan Milne
2026-03-10 18:05 ` John Garry
2026-03-10 18:42 ` Benjamin Marzinski
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=aZTL8srSowTU81Rz@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bvanassche@acm.org \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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