[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a6b9db95-a7f0-d1f6-1fa2-8dc13a6aa29e@deltatee.com>
Date: Thu, 15 Aug 2019 10:06:56 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Max Gurtovoy <maxg@...lanox.com>, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Cc: Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [PATCH v7 08/14] nvmet-core: allow one host per passthru-ctrl
On 2019-08-15 6:36 a.m., Max Gurtovoy wrote:
>
> On 8/2/2019 2:45 AM, Logan Gunthorpe wrote:
>> This patch rejects any new connection to the passthru-ctrl if this
>> controller is already connected to a different host. At the time of
>> allocating the controller we check if the subsys associated with
>> the passthru ctrl is already connected to a host and reject it
>> if the hostnqn differs.
>
> This is a big limitation.
>
> Are we plan to enable many front-end ctrl's to connect to the single
> back-end ctrl in the future ?
Honestly, I don't know that it's really necessary, but the limitation
was requested by Sagi the first time this patch-set was submitted[1]
citing unspecified user troubles. If there's consensus to remove the
restriction I certainly can.
Logan
[1] http://lists.infradead.org/pipermail/linux-nvme/2018-April/016588.html
Powered by blists - more mailing lists