linux-kernel - Re: [PATCH v5 4/5] null

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150725062511.GA26437@infradead.org>
Date:	Fri, 24 Jul 2015 23:25:11 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	Matias Bj?rling <mb@...htnvm.io>
Cc:	axboe@...com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
	Stephen.Bates@...s.com, keith.busch@...el.com
Subject: Re: [PATCH v5 4/5] null_blk: LightNVM support

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/