Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Nilay Shroff <nilay@linux.ibm.com>,
	Daniel Wagner <dwagner@suse.de>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme-multipath: expose path_state via sysfs
Date: Wed, 24 Jun 2026 09:36:32 +0800	[thread overview]
Message-ID: <5f8ea7b9-e57b-4b7f-a98b-08ec7f06cbcd@linux.alibaba.com> (raw)
In-Reply-To: <ajp9gHepQX-j1-Lz@kbusch-mbp>



在 2026/6/23 20:35, Keith Busch 写道:
> On Mon, Jun 22, 2026 at 09:03:18PM +0800, Guixin Liu wrote:
>> The attribute reflects the result of nvme_path_is_disabled() checks:
>>    - "enabled"                   : path is available for I/O
>>    - "disabled (ctrl_down)"      : controller is not live/deleting
>>    - "disabled (ana_pending)"    : ANA state change pending
>>    - "disabled (ns_not_ready)"   : namespace is not ready
> I'm a bit late to looking at this, but just a knee jerk thought,
> wouldn't you want to distinguish "enabled optimized" vs "enabled
> unoptimized"?
Sure, good idea, I will change this in v3, thanks.

Best Regards,
Guixin Liu



      parent reply	other threads:[~2026-06-24  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 13:03 [PATCH v2] nvme-multipath: expose path_state via sysfs Guixin Liu
2026-06-23  6:16 ` Nilay Shroff
2026-06-23  7:54   ` Guixin Liu
2026-06-23 12:35 ` Keith Busch
2026-06-23 14:01   ` Nilay Shroff
2026-06-24  1:36   ` 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=5f8ea7b9-e57b-4b7f-a98b-08ec7f06cbcd@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=dwagner@suse.de \
    --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