Skip to content

libnvme: add CIU and CIRN to Identify Controller data structure#3426

Open
MaisenbacherD wants to merge 1 commit into
linux-nvme:masterfrom
MaisenbacherD:id-ctrl-ciu-cirn
Open

libnvme: add CIU and CIRN to Identify Controller data structure#3426
MaisenbacherD wants to merge 1 commit into
linux-nvme:masterfrom
MaisenbacherD:id-ctrl-ciu-cirn

Conversation

@MaisenbacherD
Copy link
Copy Markdown
Contributor

@igaw As we discussed at Lund Linux Conference, I took the spec and cross-referenced it with the code base to an LLM. It found some discrepancies. Here is the first one. Please let me know if this is useful, I will then continue sending the next ones in batches after manually checking the mismatches. :)

Commit description :

The I/O Command Set Independent Identify Controller data structure (Figure 328 in NVM Express Base Specification 2.3) defines two fields that were previously hidden inside the rsvd135[118] reserved block:

  • byte 135 Controller Instance Uniquifier (CIU)
  • bytes 143:136 Controller Instance Random Number (CIRN)

Split rsvd135[118] into ciu, cirn[8], and the two remaining reserved ranges.

Assisted-by: Claude:claude-opus-4-8 [devin]

The I/O Command Set Independent Identify Controller data structure
(Figure 328 in NVM Express Base Specification 2.3) defines two fields
that were previously hidden inside the rsvd135[118] reserved block:

  - byte 135    Controller Instance Uniquifier (CIU)
  - bytes 143:136 Controller Instance Random Number (CIRN)

Split rsvd135[118] into ciu, cirn[8], and the two remaining reserved
ranges.

Signed-off-by: Dennis Maisenbacher <dennis.maisenbacher@wdc.com>
Assisted-by: Claude:claude-opus-4-8 [devin]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant