public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Wen Xiong <wenxiong@linux.ibm.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, Wenxiong <wenxiong@us.ibm.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: nvme native multipath question with two physical paths
Date: Mon, 19 Feb 2024 15:55:16 -0600	[thread overview]
Message-ID: <03df8d694cd982973c7c2c08f1d4379a@linux.ibm.com> (raw)
In-Reply-To: <ZdOrzKNn-ryJ8v-i@kbusch-mbp>

On 2024-02-19 13:28, Keith Busch wrote:

> Nor should you see a /dev/nvme6n1 in this scenario. The mulitpath 
> device
> doesn't change names. It assumes the identifier from the subsystem. In
> your example, it uses subsystem '2' and will continue to use it no
> matter which controller instances are attach to it. This feature is why
> applications that have opened the /dev/nvme2n1 handle  don't need to do
> anything if the kernel experiences a path failover condition.
> 
> You should see the different paths in the hidden block hierarchy, which
> you can find in the sysfs directory. There should be an entry in your
> example at /sys/block/nvme2c6n1/. I am pretty sure  programs like
> 'iostat' can show how IO is distributed among all the paths of an nvme
> mulitpath device.

Hi Ketith,

Thanks for your detail explanation!
Wendy


      reply	other threads:[~2024-02-19 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 19:03 nvme native multipath question with two physical paths Wen Xiong
2024-02-19 19:28 ` Keith Busch
2024-02-19 21:55   ` Wen Xiong [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=03df8d694cd982973c7c2c08f1d4379a@linux.ibm.com \
    --to=wenxiong@linux.ibm.com \
    --cc=hch@infradead.org \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=wenxiong@us.ibm.com \
    /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