On 28/03/2018 10.28, Christoph Hellwig wrote:
I really don't want more lightnvm cruft in the core. We'll need
a proper abstraction.c
I agree, we should get that moving, and make a proper abstraction for
it. Also with respect to how an SMR interface in general is integrated
into NVMe.
The
I really don't want more lightnvm cruft in the core. We'll need
a proper abstraction.c
On Fri, Mar 23, 2018 at 12:00:08PM +0100, Matias Bjørling wrote:
> On 02/05/2018 01:15 PM, Matias Bjørling wrote:
> > The nvme driver sets up the size of the nvme namespace in two steps.
> > First it initialize
On 02/05/2018 01:15 PM, Matias Bjørling wrote:
The nvme driver sets up the size of the nvme namespace in two steps.
First it initializes the device with standard logical block and
metadata sizes, and then sets the correct logical block and metadata
size. Due to the OCSSD 2.0 specification relies
The nvme driver sets up the size of the nvme namespace in two steps.
First it initializes the device with standard logical block and
metadata sizes, and then sets the correct logical block and metadata
size. Due to the OCSSD 2.0 specification relies on the namespace to
expose these sizes for correc
4 matches
Mail list logo
