[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05a74e81-1dbd-725f-1369-5ca5c5918db1@mellanox.com>
Date: Thu, 15 Aug 2019 15:36:02 +0300
From: Max Gurtovoy <maxg@...lanox.com>
To: Logan Gunthorpe <logang@...tatee.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 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 ?
I guess it can be incremental to this series.
Powered by blists - more mailing lists