[PATCH V3 00/19] lightnvm: pblk: implement 2.0 support
Javier Gonzalez
javier at cnexlabs.com
Mon Feb 26 10:21:30 PST 2018
> On 26 Feb 2018, at 19.19, Matias Bjørling <mb at lightnvm.io> wrote:
>
> On 02/26/2018 02:16 PM, Javier González wrote:
>> # Changes since V2:
>> Apply Matias' feedback:
>> - Remove generic nvm_id identify structure.
>> - Do not remap capabilities (cap) to media and controlled capabilities
>> (mccap). Instead, add a comment to prevent confusion when
>> crosschecking with 2.0 spec.
>> - Change maxoc and maxocpu defaults from 1 block to the max number of
>> blocks.
>> - Re-implement the generic geometry to use nvm_geo on both device and
>> targets. Maintain nvm_common_geo to make it easier to copy the common
>> part of the geometry (without having to overwrite target-specific
>> fields, which is ugly and error prone). Matias, if you still want to
>> get rid of this, we can do it.
>
> I do, the variables should go directly in nvm_geo. Thanks.
Ok. Is the rest ok with you?
Javier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180226/f51415d6/attachment.sig>
More information about the Linux-nvme
mailing list