From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@wdc.com>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] nvmet: per-host namespaces masking
Date: Fri, 5 Feb 2021 10:40:43 +0100 [thread overview]
Message-ID: <20210205094043.GA2694@lst.de> (raw)
In-Reply-To: <e505e360-ec8a-ba06-4a40-bf9d2006a7a0@suse.de>
On Fri, Feb 05, 2021 at 10:38:41AM +0100, Hannes Reinecke wrote:
> On 2/5/21 10:32 AM, Christoph Hellwig wrote:
>> On Fri, Feb 05, 2021 at 10:29:26AM +0100, Hannes Reinecke wrote:
>>> Implement per-host namespaces masking, allowing to expose
>>> different namespaces to different hosts connecting to the
>>> same subsystem.
>>> The original method of adding host nqns to the subsystem
>>> takes precedence over the per-host namespace masking.
>>
>> Why do you want to expose a single subsystem to multiple hosts? This
>> creates all kinds of covert channels better avoided.
>>
> But the alternative is a subsystem per host.
> Which leads to a proliferation of subsystems on the target.
Yes, that was the choice we had in mind when writing the code. The
subsystems are very cheap as they don't require any resources except
for some fairly small memory allocations.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-05 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 9:29 [PATCH] nvmet: per-host namespaces masking Hannes Reinecke
2021-02-05 9:32 ` Christoph Hellwig
2021-02-05 9:38 ` Hannes Reinecke
2021-02-05 9:40 ` Christoph Hellwig [this message]
2021-02-05 18:42 ` 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=20210205094043.GA2694@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--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