nvme_get_lo...odel_ddc_req(2)

✨ NAME ✨

nvme_get_log_pull_model_ddc_req — bestie, this one pulls the Pull Model DDC Request Log for you 💅

---

🌸 SYNOPSIS 🌸

int nvme_get_log_pull_model_ddc_req (int fd , bool rae , __u32 len ,
       struct nvme_pull_model_ddc_req_log *log );

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of your nvme device. like, the doorway to the whole thing 🚪✨
• rae — Retain asynchronous events. yes ma'am, keep 'em 👑
• len — how much space you allocated for the log page. the allocated length, periodt 📏
• log — the user address where the log page is gonna get stored. drop it right there 🫶

---

💖 RETURN 💖

Okay so here's the tea: if a response came back, you get the nvme command status (peep enum nvme_status_field for that whole situation 👀). Otherwise it's -1 and errno gets set. so like, either the status or the classic -1 + errno combo. no in-between, fr fr 😭

heads up bestie: -1 means look at errno, not the vibes 🌈

---

and that's the whole page, no cap 💜 this was the libnvme API manual, dated July 2026 — thanks for reading my lil manpage era, mwah 🎀✨🦋