From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Keith Busch via Lsf-pc <lsf-pc@lists.linux-foundation.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
Keith Busch <kbusch@kernel.org>,
John Garry <john.g.garry@oracle.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Native SCSI multipath support
Date: Tue, 17 Feb 2026 21:39:10 -0500 [thread overview]
Message-ID: <yq1seaydbee.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <aZTL8srSowTU81Rz@kbusch-mbp> (Keith Busch via Lsf-pc's message of "Tue, 17 Feb 2026 13:13:38 -0700")
Keith,
> For nvme, we can detect if a device is multipath capable.
Yep. Same with SCSI...
--
Martin K. Petersen
next prev parent reply other threads:[~2026-02-18 2:39 UTC|newest]
Thread overview: 23+ 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 15:26 ` Fwd: " Xose Vazquez Perez
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
2026-02-18 2:39 ` Martin K. Petersen [this message]
2026-02-18 7:35 ` [Lsf-pc] " 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=yq1seaydbee.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--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 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.