Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-28 Thread Matias Bjørling
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

Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-28 Thread Matias Bjørling
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

Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-28 Thread Christoph Hellwig
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

Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-28 Thread Christoph Hellwig
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

Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-23 Thread Matias Bjørling
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

Re: [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-03-23 Thread Matias Bjørling
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

[PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-02-05 Thread Matias Bjørling
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

[PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-02-05 Thread Matias Bjørling
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