[RFC PATCH 3/3] nvme: add the "debug" host driver
Luis Chamberlain
mcgrof at kernel.org
Thu Feb 3 11:34:27 PST 2022
On Thu, Feb 03, 2022 at 05:15:34PM +0100, Christoph Hellwig wrote:
> On Thu, Feb 03, 2022 at 08:06:33AM -0800, Luis Chamberlain wrote:
> > On Wed, Feb 02, 2022 at 06:01:13AM +0000, Adam Manzanares wrote:
> > > BTW I think having the target code be able to implement simple copy without
> > > moving data over the fabric would be a great way of showing off the command.
> >
> > Do you mean this should be implemented instead as a fabrics backend
> > instead because fabrics already instantiates and creates a virtual
> > nvme device? And so this would mean less code?
>
> It would be a lot less code. In fact I don't think we need any new code
> at all. Just using nvme-loop on top of null_blk or brd should be all
> that is needed.
Mikulas,
That begs the question why add this instead of using null_blk with
nvme-loop?
Luis
More information about the Linux-nvme
mailing list