libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ‘‘ libnvme(9) β€” the API Manual, bestie edition πŸ‘‘

okay so real talk, this page is from the libnvme(9) API Manual and it's literally just one little enum, but it's an important little enum, so let's give it the attention it deserves πŸ’…


✨ NAME ✨

enum nvme_rate_limiting_target β€” the Rate Limiting Feature Command Dword 11 Target (TGT), no cap 🎯

Like, that's the whole name. It's the thing that tells you where the rate limiting is aimed. TGT. Dword 11. Iconic behavior honestly.


🌸 SYNOPSIS 🌸

here's the whole vibe, copy it exactly bestie:

enum nvme_rate_limiting_target {
    NVME_RATE_LIMITING_TARGET_CONTROLLER ,
    NVME_RATE_LIMITING_TARGET_VENDOR_MIN ,
    NVME_RATE_LIMITING_TARGET_VENDOR_MAX

};

three constants, one enum, zero drama 🫢


πŸ’œ Constants πŸ’œ

so these are the actual members and what each one means, fr fr:

  • NVME_RATE_LIMITING_TARGET_CONTROLLER β€” the Target Identifier field here specifies the controller identifier πŸŽ€ like, the target is a controller, that's the whole assignment.
  • NVME_RATE_LIMITING_TARGET_VENDOR_MIN β€” this one marks the start of the vendor specific range πŸ¦‹ it's the beginning of the "vendors do whatever they want in here" zone.
  • NVME_RATE_LIMITING_TARGET_VENDOR_MAX β€” and this one marks the end of the vendor specific range 🌈 the boundary, the edge, the closing tag of the vendor zone.

ngl this page is short and sweet, but every single constant is up there β€” CONTROLLER, VENDOR_MIN, VENDOR_MAX β€” in the exact same order as the source. don't sleep on the min/max pairing, it's giving bookends πŸ’€

and that's the whole page, bestie ✨ this was the libnvme(9) API Manual, October 2026 edition, and I hope it slayed for you πŸ’– libnvme(9) forever, periodt πŸ‘‘

πŸ“¦ where this page comes from