Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-multipath: expose path_state via sysfs
Date: Mon, 22 Jun 2026 17:09:18 +0800	[thread overview]
Message-ID: <231abfaf-700c-4d62-b2ff-652da52d5109@linux.alibaba.com> (raw)
In-Reply-To: <38c7c98a-03cf-4c35-90d5-d7557eaa8a4d@linux.ibm.com>

>
> Instead of only exposing disabled/enabled state, can we also expose the
> reason why the path was not usable?
>
> For instance, path_state attribute shall expose "enabled" when it's
> available for I/O (this is straightforward):
> - enabled
>
> But in case path is not usable/available then expose "disabled" along
> with the reason:
> - disabled (ctrl_down)
> - disabled (ana_pending)
> - disabled (ns_not_ready)
>
> Or any other combination depending on the ns->flags and ctrl->state.
>
> That way, the userspace would know the exact reason when path is
> not available/usable for I/O.
>
> Thanks,
> --Nilay
Good idea, I will add this in v2, thanks.

Best Regards,
Guixin Liu



      reply	other threads:[~2026-06-22  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 12:15 [PATCH] nvme-multipath: expose path_state via sysfs Guixin Liu
2026-06-18 13:02 ` Daniel Wagner
2026-06-22  2:02   ` Guixin Liu
2026-06-22  7:50     ` Daniel Wagner
2026-06-22  9:07       ` Guixin Liu
2026-06-22  5:10 ` Nilay Shroff
2026-06-22  9:09   ` Guixin Liu [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=231abfaf-700c-4d62-b2ff-652da52d5109@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.com \
    --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