From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 3/3] nvmet: include all configured ports in the discovery log page
Date: Thu, 7 Apr 2022 15:34:01 +0200 [thread overview]
Message-ID: <20220407133401.GA7294@lst.de> (raw)
In-Reply-To: <f28bed4d-a5a5-b1e4-020e-c76ded479c5b@suse.de>
On Thu, Apr 07, 2022 at 03:31:51PM +0200, Hannes Reinecke wrote:
> On 4/7/22 15:29, Sagi Grimberg wrote:
>>
>>> When a per-port discovery subsystem is used we should include
>>> all configured ports in the discovery log page, not just that one
>>> through which the controller was connected.
>>
>> Why?
>>
> Because that's the whole point if it being configurable.
I'm really confused about this. Please try to explain "the whole point"
a bit better.
next prev parent reply other threads:[~2022-04-07 13:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 10:48 [PATCHv4 0/3] nvmet: unique discovery subsystems Hannes Reinecke
2022-04-07 10:48 ` [PATCH 1/3] nvmet: make the subsystem type configurable Hannes Reinecke
2022-04-07 15:44 ` Christoph Hellwig
2022-04-07 16:55 ` Hannes Reinecke
2022-04-08 5:46 ` Christoph Hellwig
2022-04-07 10:48 ` [PATCH 2/3] nvmet: per-port discovery subsystem Hannes Reinecke
2022-04-07 15:49 ` Christoph Hellwig
2022-04-07 17:21 ` Hannes Reinecke
2022-04-08 5:48 ` Christoph Hellwig
2022-04-07 10:48 ` [PATCH 3/3] nvmet: include all configured ports in the discovery log page Hannes Reinecke
2022-04-07 13:29 ` Sagi Grimberg
2022-04-07 13:31 ` Hannes Reinecke
2022-04-07 13:34 ` Christoph Hellwig [this message]
2022-04-07 13:38 ` Sagi Grimberg
2022-04-07 14:51 ` Hannes Reinecke
2022-04-07 15:38 ` Christoph Hellwig
2022-04-07 15:41 ` Christoph Hellwig
2022-04-07 17:25 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 6:59 [PATCHv5 0/3] nvmet: unique discovery subsystems Hannes Reinecke
2022-04-08 6:59 ` [PATCH 3/3] nvmet: include all configured ports in the discovery log page Hannes Reinecke
2022-04-11 10:54 ` Sagi Grimberg
2022-04-11 12:27 ` Hannes Reinecke
2022-04-12 10:49 ` Sagi Grimberg
2022-04-12 12:08 ` Hannes Reinecke
2022-04-12 12:29 ` Sagi Grimberg
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=20220407133401.GA7294@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--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 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.