nvme_mi_adm...le_lat_event(2)

✨ NAME ✨

nvme_mi_admin_get_log_predictable_lat_event — bestie, this is the one that goes and Retrieves the Predictable Latency Event Aggregate Log Page 💖

So yeah, the manual name is <rainbow>libnvme API manual</rainbow> and this page is all about that predictable-latency-tea ☕✨

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_predictable_lat_event (nvme_mi_ctrl_t ctrl ,
bool rae , __u32 offset , __u32 len , void *log );

No cap, that's the whole signature. Five args, one int coming back at you 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller you're querying, like, the whole reason we're here 🫶
• rae — Retain asynchronous events. It's a bool, so true/false energy only ✨
• offset — Offset into the predictable latency event. Yes, an __u32 😌
• len — Length of provided user buffer to hold the log data, in bytes. Counts in bytes, not vibes 💀
• log — User address for the log page data. It's a void *, so it's giving mysterious-but-that's-the-point 🌈

---

💜 RETURN 💜

The nvme command status if a response was received — peep enum nvme_status_field for the full menu of what that could be 👑

or, and hear me out 😭, -1 with errno set otherwise. That's the bad ending. errno will tell you the story fr fr.

---

okay that's the whole page, and it's iconic, periodt 🎀 The footer tea? This is from the libnvme API manual, dated July 2026, and the page is nvme_mi_adm...le_lat_event(2) — yeah the title got truncated in the footer, happens to the best of us 💅 Stay predictable, stay latency-logged, love u 🦋✨