libnvme_mi_admin_xfer(9)

💅 libnvme_mi_admin_xfer

okay bestie, welcome to the libnvme API manual — this one's the raw admin transfer interface, and it is literally the main character of "just send the thing to the controller already" 🎀

---

✨ NAME ✨

libnvme_mi_admin_xfer — raw admin transfer interface, fr fr.

---

🌸 SYNOPSIS 🌸

int libnvme_mi_admin_xfer (struct libnvme_transport_handle *hdl , struct
       nvme_mi_admin_req_hdr *admin_req , size_t req_data_size , struct
       nvme_mi_admin_resp_hdr *admin_resp , off_t resp_data_offset , size_t
       *resp_data_size );

like… six arguments, no cap. she's built different 😤

---

🦋 ARGUMENTS 🦋

• hdl — the transport handle you're sending the admin command to. this is your ride 👑
• admin_req — request data. the actual ask 💌
• req_data_size — size of request data payload. payload only, bestie — not the header 📏
• admin_resp — buffer for response data. where the controller's reply lands 🫶
• resp_data_offset — offset into request data to retrieve from controller. yeah, that's what it says — keep it exactly like that, don't @ me 🙈
• resp_data_size — size of response data buffer, updated to received size. she goes in as a size and comes out as the size ✨

---

💜 DESCRIPTION 💜

So what this does: it performs an arbitrary NVMe Admin command, using the provided request data in admin_req. simple as that, lowkey iconic.

the size of the request data payload is specified in req_data_size — and listen, this does not include the standard header length. so a header-only request would have a size of 0. zero. nada. that's not a bug, that's the vibe check ✅

On success, response data is stored in admin_resp, which has an optional appended payload buffer of resp_data_size bytes. The actual payload transferred will be stored in resp_data_size (she updates herself, we love a self-aware buffer 💅). These sizes do not include the Admin request header, so 0 represents no payload. same rules, both directions 🪞

As with all Admin commands, we can request partial data from the Admin Response payload, offset by resp_data_offset. partial reads ate, honestly 🔥

See: struct nvme_mi_admin_req_hdr and struct nvme_mi_admin_resp_hdr. go look at the structs bestie, iykyk 🧚

---

⭐ RETURN ⭐

The nvme command status if a response was received (see enum nvme_status_field) or a negative error code otherwise. so either you get a status, or you get a negative number and a little sadness 😭

---

and that's the whole page, bestie — go forth and xfer 🌈🦋

this has been the libnvme API manual, dated October 2026 — libnvme_mi_admin_xfer(9) out 💖 slay, bye 👋