From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH v5 4/5] null_blk: LightNVM support Date: Fri, 24 Jul 2015 23:25:11 -0700 Message-ID: <20150725062511.GA26437@infradead.org> References: <1437587464-7964-1-git-send-email-mb@lightnvm.io> <1437587464-7964-5-git-send-email-mb@lightnvm.io> <20150723095351.GB26420@infradead.org> <55B0C660.8010509@lightnvm.io> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: axboe@fb.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, Stephen.Bates@pmcs.com, keith.busch@intel.com To: Matias Bj?rling Return-path: Content-Disposition: inline In-Reply-To: <55B0C660.8010509@lightnvm.io> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Jul 23, 2015 at 12:48:00PM +0200, Matias Bj?rling wrote: > Only reason was to not duplicate the I/O submission/completion flow. > With the simple code at the moment, it is little to add. However, if > someone decides to put backing store, simulation, etc. into it, then it > should properly go into another module. > > Do you want me to move it into a new driver for this patchset? I'd prefer to have it separate unless there's a good reason to merge it into null_blk. From your above descriptions it sounds like it really should be separate.