Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-22 Thread Javier Gonzalez
> On 22 Feb 2018, at 13.22, Matias Bjørling wrote: > > On 02/22/2018 08:44 AM, Javier Gonzalez wrote: >>> On 22 Feb 2018, at 08.25, Matias Bjørling wrote: >>> >>> On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-22 Thread Javier Gonzalez
> On 22 Feb 2018, at 13.22, Matias Bjørling wrote: > > On 02/22/2018 08:44 AM, Javier Gonzalez wrote: >>> On 22 Feb 2018, at 08.25, Matias Bjørling wrote: >>> >>> On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored redundantly in the nvm_id and

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-22 Thread Matias Bjørling
On 02/22/2018 08:44 AM, Javier Gonzalez wrote: On 22 Feb 2018, at 08.25, Matias Bjørling wrote: On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-22 Thread Matias Bjørling
On 02/22/2018 08:44 AM, Javier Gonzalez wrote: On 22 Feb 2018, at 08.25, Matias Bjørling wrote: On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when instantiating targets on

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Javier Gonzalez
> On 22 Feb 2018, at 08.25, Matias Bjørling wrote: > > On 02/21/2018 10:26 AM, Javier González wrote: >> Currently, the device geometry is stored redundantly in the nvm_id and >> nvm_geo structures at a device level. Moreover, when instantiating >> targets on a specific number

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Javier Gonzalez
> On 22 Feb 2018, at 08.25, Matias Bjørling wrote: > > On 02/21/2018 10:26 AM, Javier González wrote: >> Currently, the device geometry is stored redundantly in the nvm_id and >> nvm_geo structures at a device level. Moreover, when instantiating >> targets on a specific number of LUNs, these

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Matias Bjørling
On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when instantiating targets on a specific number of LUNs, these structures are replicated and manually modified to fit the instance

Re: [PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Matias Bjørling
On 02/21/2018 10:26 AM, Javier González wrote: Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when instantiating targets on a specific number of LUNs, these structures are replicated and manually modified to fit the instance

[PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Javier González
Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when instantiating targets on a specific number of LUNs, these structures are replicated and manually modified to fit the instance channel and LUN partitioning. Instead, create a

[PATCH 01/20] lightnvm: simplify geometry structure.

2018-02-21 Thread Javier González
Currently, the device geometry is stored redundantly in the nvm_id and nvm_geo structures at a device level. Moreover, when instantiating targets on a specific number of LUNs, these structures are replicated and manually modified to fit the instance channel and LUN partitioning. Instead, create a