From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 20 Sep 2017 16:54:36 +0200 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Jens Axboe , Keith Busch , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-block@vger.kernel.org Subject: Re: [PATCH 8/9] nvme: track shared namespaces Message-ID: <20170920145436.GA4709@lst.de> References: <20170918231453.27128-1-hch@lst.de> <20170918231453.27128-9-hch@lst.de> <20170920083643.xe6dbr4iu53hhm5t@linux-x5ow.site> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20170920083643.xe6dbr4iu53hhm5t@linux-x5ow.site> List-ID: On Wed, Sep 20, 2017 at 10:36:43AM +0200, Johannes Thumshirn wrote: > Being one of the persons who has to backport a lot of NVMe code to older > kernels I'm not a huge fan of renaming nmve_ns. The churn is main main worry. Well and that I don't have a reall good name for what currently is nvme_ns either :) > That said, I don't have a better name for nvme_ns_head (yet) but I'll try to > think of one as well. OTOH looking at nvme_ns_head it actaully is the list > head of the nvme_ns list. But head also has connotations in the SAN world. Maybe nvme_ns_chain? From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Wed, 20 Sep 2017 16:54:36 +0200 Subject: [PATCH 8/9] nvme: track shared namespaces In-Reply-To: <20170920083643.xe6dbr4iu53hhm5t@linux-x5ow.site> References: <20170918231453.27128-1-hch@lst.de> <20170918231453.27128-9-hch@lst.de> <20170920083643.xe6dbr4iu53hhm5t@linux-x5ow.site> Message-ID: <20170920145436.GA4709@lst.de> On Wed, Sep 20, 2017@10:36:43AM +0200, Johannes Thumshirn wrote: > Being one of the persons who has to backport a lot of NVMe code to older > kernels I'm not a huge fan of renaming nmve_ns. The churn is main main worry. Well and that I don't have a reall good name for what currently is nvme_ns either :) > That said, I don't have a better name for nvme_ns_head (yet) but I'll try to > think of one as well. OTOH looking at nvme_ns_head it actaully is the list > head of the nvme_ns list. But head also has connotations in the SAN world. Maybe nvme_ns_chain?