From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@wdc.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-multipath: add an 'ana_groups_only' module option
Date: Wed, 9 Feb 2022 14:57:55 +0100 [thread overview]
Message-ID: <20220209135755.GA20679@lst.de> (raw)
In-Reply-To: <7bef474d-f6c4-0ecc-3a5b-44a310e2e026@suse.de>
On Wed, Feb 09, 2022 at 09:49:16AM +0100, Hannes Reinecke wrote:
> How so?
> I'm just reverting the check; instead of having the nsid listed in the ana
> log page and check for a match between the nsids we now check for a match
> between the group id in the ana log page and the ana grpid from the
> 'identify namespace' output.
> So I'm still able to identify which namespace this change belongs to.
And how this this catching namespaces that move between ANA groups?
How does it deal with the hang fixed by Anton in commit af8fd0424713?
next prev parent reply other threads:[~2022-02-09 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 10:00 [PATCH] nvme-multipath: add an 'ana_groups_only' module option Hannes Reinecke
2022-02-07 12:37 ` Sagi Grimberg
2022-02-07 13:00 ` Hannes Reinecke
2022-02-09 8:07 ` Christoph Hellwig
2022-02-09 8:49 ` Hannes Reinecke
2022-02-09 13:57 ` Christoph Hellwig [this message]
2022-02-10 2:52 ` John Meneghini
2022-02-10 5:43 ` Christoph Hellwig
2022-02-10 8:17 ` Hannes Reinecke
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=20220209135755.GA20679@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--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