Update nvmeadm identify to 1.4
We should update the output of
nvmeadm identify for both the primary namespace and controller today only knows about NVMe 1.1. We should update this to know about NVMe 1.4. This'll both help users know what's going on with their devices and help developers figure out where to continue to expand nvmeadm.
Updated by Robert Mustacchi about 1 year ago
To test this I looked at the nvmeadm output from several NVMe 1.3 and 1.4 devices from folks including:
For each of these I looked at the verbose
identify output for both the controller and the main namespace before and after this change. The main differences that weren't just formatting were identification of the number of blocks for atomic/CAS related operations because it wasn't properly checking the feature bit in the past. Otherwise, various spot checks of data seemed to line up.
Updated by Electric Monk about 1 year ago
- Status changed from New to Closed
- % Done changed from 80 to 100
commit 8d5300d3859436fa82e7199f50011911090c65dc Author: Robert Mustacchi <email@example.com> Date: 2021-03-10T17:05:39.000Z 13530 Update nvmeadm identify to 1.4 Reviewed by: C Fraire <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>