Re: [GIT PULL 18/20] lightnvm: pblk: handle case when mw_cunits equals to 0

> On 28 May 2018, at 10.58, Matias Bjørling wrote: > > From: Marcin Dziegielewski > > Some devices can expose mw_cunits equal to 0, it can cause creation > of too small write buffer and cause performance to drop on write > workloads. > > To

Re: [GIT PULL 18/20] lightnvm: pblk: handle case when mw_cunits equals to 0

> On 28 May 2018, at 10.58, Matias Bjørling wrote: > > From: Marcin Dziegielewski > > Some devices can expose mw_cunits equal to 0, it can cause creation > of too small write buffer and cause performance to drop on write > workloads. > > To handle that, we use the default value for MLC and

[GIT PULL 18/20] lightnvm: pblk: handle case when mw_cunits equals to 0

From: Marcin Dziegielewski Some devices can expose mw_cunits equal to 0, it can cause creation of too small write buffer and cause performance to drop on write workloads. To handle that, we use the default value for MLC and beacause it covers both 1.2 and 2.0 OC

[GIT PULL 18/20] lightnvm: pblk: handle case when mw_cunits equals to 0

From: Marcin Dziegielewski Some devices can expose mw_cunits equal to 0, it can cause creation of too small write buffer and cause performance to drop on write workloads. To handle that, we use the default value for MLC and beacause it covers both 1.2 and 2.0 OC specification, setting up