From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>,
chengjike <chengjike.cheng@huawei.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "sunao.sun@huawei.com" <sunao.sun@huawei.com>,
"jiangtao62@huawei.com" <jiangtao62@huawei.com>
Subject: Re: [PATCH V3 nvme-cli 1/2] initialize disk "access" variable
Date: Tue, 28 Sep 2021 21:18:24 +0000 [thread overview]
Message-ID: <4865cf81-9b27-d797-2c01-53904271221e@nvidia.com> (raw)
In-Reply-To: <e916dbea-8796-5ed1-06f6-4d89c72f3b69@grimberg.me>
> Also live/faulty is not a good terminology for path access.
> Maybe full/partial or complete/incomplete.
>
> I thought that this was about showing the completeness of the
> path access for a given ns, regardless of failure of identify-ns...
>
since printing the path access and id-ns are two different things,
id-ns can fail and we still can read the path access that is why
we should make this an optional print with command line arg feature,
if it has been considered yet ...
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-09-28 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 8:50 [PATCH V3 nvme-cli 0/2] add "Path Access" field in command "nvme list" chengjike
2021-09-28 8:50 ` [PATCH V3 nvme-cli 1/2] initialize disk "access" variable chengjike
2021-09-28 20:45 ` Sagi Grimberg
2021-09-28 21:18 ` Chaitanya Kulkarni [this message]
2021-10-08 12:23 ` Chengjike (ISSP)
2021-09-28 8:50 ` [PATCH V3 nvme-cli 2/2] add "Path Access" entry in command output chengjike
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=4865cf81-9b27-d797-2c01-53904271221e@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=chengjike.cheng@huawei.com \
--cc=jiangtao62@huawei.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sunao.sun@huawei.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 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.