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

2018-02-15 Thread Matias Bjørling
On 02/12/2018 09:21 PM, Javier Gonzalez wrote: On 9 Feb 2018, at 01.27, 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

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

2018-02-15 Thread Matias Bjørling
On 02/12/2018 09:21 PM, Javier Gonzalez wrote: On 9 Feb 2018, at 01.27, 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

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

2018-02-12 Thread Javier Gonzalez
> On 9 Feb 2018, at 01.27, 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

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

2018-02-12 Thread Javier Gonzalez
> On 9 Feb 2018, at 01.27, 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

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

2018-02-09 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 V2 4/4] nvme: lightnvm: add late setup of block size and metadata

2018-02-09 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