libnvme(9)

💖 NAME 💖

struct nvme_directive_recv_args — the lil argument bundle you hand over for the NVMe Directive Receive command, bestie ✨

---

🌸 SYNOPSIS 🌸

struct nvme_directive_recv_args {
    __u32 *result;
    void *data;
    int args_size;
    int fd;
    __u32 timeout;
    __u32 nsid;
    enum nvme_directive_receive_doper doper;
    enum nvme_directive_dtype dtype;
    __u32 cdw12;
    __u32 data_len;
    __u16 dspec;
 };

---

🎀 Members 🎀

Okay so this is the whole cast, and every single one of them has main character energy in their own way 👑

• result — if everything goes slay, this is where the CQE dword0 value lands. it's a __u32 *, so a pointer, not a vibe. 🫶
• data — the userspace address of the data payload. literally where your actual bytes live. ✨
• args_size — the size of struct nvme_directive_recv_args. yes it's self-referential, no it's not a mirror selfie, it's just struct bookkeeping. 💅
• fd — file descriptor of the nvme device. your ticket to the party, no cap. 🎟️
• timeout — timeout in ms. the clock is ticking bestie ⏰
• nsid — Namespace ID, if applicable. so like, sometimes it's relevant, sometimes it's not. read the room. 🦋
• doper — Directive send operation, see enum nvme_directive_send_doper. (yes, this is the receive command and the doc points you at the send enum — that's what it says, and I am simply the messenger 🙈)
• dtype — Directive type, see enum nvme_directive_dtype. pick your fighter. 🔥
• cdw12 — Directive specific command dword12. iconic little dword. ⭐
• data_len — Length of data payload in bytes. count 'em, don't guess. 🌈
• dspec — Directive specific field. a __u16, so keep it smol and cute. 🍓

ngl bestie, this whole struct is just a lil envelope of args — nothing here is dangerous, but a wrong args_size or a bogus fd will absolutely humble you. vibe check your inputs first. 💀

---

that's the whole page, fr fr 🧚

this was brought to you by libnvme(9) — API Manual — dated August 2026, and the page itself is struct nvme_directive_recv_args. periodt. 👑💜