nvme_init_g...le_lat_event(9)

💖 nvme_init_get_log_predictable_lat_event — the libnvme API manual, but make it make sense ✨

Okay bestie, gather round, because today we're meeting nvme_init_get_log_predictable_lat_event(9) from the libnvme API manual, and honestly? She's a little helper with a big name and I'm obsessed. 🎀

---

🌸 NAME 🌸

nvme_init_get_log_predictable_lat_event — literally the function that initializes the passthru command for the Predictable Latency Event Aggregate. Say that five times fast, I dare you. 💅

---

✨ SYNOPSIS ✨

void nvme_init_get_log_predictable_lat_event (struct libnvme_passthru_cmd *cmd ,
                                              __u64 lpo ,
                                              void *log ,
                                              __u32 len );

No cap, she returns void — she's not here to give you answers, she's here to set things up. Main character energy only. 👑

---

🦋 ARGUMENTS 🦋

Four little besties walk into a function call:

• cmd — the passthru command you're gonna use. This is the one getting glowed up. 💖
• lpo — offset into the predictable latency event. Type <italic>__u64</italic>, because we're fancy like that. 🔥
• log — the user address for the log page data. i.e. where the good stuff gets parked. 📍
• len — length of the user buffer that's holding the log data, measured in bytes. Type <italic>__u32</italic>. Measure twice, bestie. 📏

---

🌈 DESCRIPTION 🌈

So what does she actually do? She initializes the passthru command buffer for the Get Log command — and she does it with the LID value NVME_LOG_LID_PREDICTABLE_LAT_AGG. That's it, that's the whole vibe check: set up the buffer, right LID, done. Slay. ⭐

Fr fr, no extra magic here — she sets up the command buffer for Get Log with NVME_LOG_LID_PREDICTABLE_LAT_AGG and hands the mic back to you. 🫶

---

Okay that's the whole page, bestie — go forth and initialize with confidence 💜

Signed, sealed, delivered: October 2026, straight from the libnvme API manual. Mwah! 😭💋