[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4b17be94-d068-f026-756f-59208075e254@nvidia.com>
Date: Thu, 13 Jul 2023 13:50:30 +0300
From: Max Gurtovoy <mgurtovoy@...dia.com>
To: Daniel Wagner <dwagner@...e.de>, Hannes Reinecke <hare@...e.de>,
g@...bon.lan
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org, Chaitanya Kulkarni <kch@...dia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>,
Sagi Grimberg <sagi@...mberg.me>,
James Smart <jsmart2021@...il.com>,
Martin Belanger <Martin.Belanger@...l.com>
Subject: Re: [PATCH blktests v1 2/3] nvme/rc: Avoid triggering host nvme-cli
autoconnect
On 13/07/2023 13:44, Daniel Wagner wrote:
> On Thu, Jul 13, 2023 at 12:30:45PM +0200, Daniel Wagner wrote:
>> On Thu, Jul 13, 2023 at 12:14:14PM +0200, Hannes Reinecke wrote:
>>>> Exposing the subsystem is from the target configuration side.
>>>> Additionally, the --context (which is in the initiator/host side),
>>>> according to Daniel, is there to distinguish between different
>>>> invocations. I proposed that blktests subsystem will not be part of
>>>> discoverable fabric or protected somehow by access list. Therefore, no
>>>> additional invocation will happen.
>>
>> I am confused. This is exactly what the whole --context thing is.
>
> Ah I think I got it now. You want me to set allow_hosts on the target side too
> :)
Yes.
With the unique hostId/hostNqn for blktests this should work without the
need for --context mechanism, that was probably added for system
administrators and not for unit_testing/QA/Verification engineers that
run blktests.
Powered by blists - more mailing lists