NVME_GET_LOG_TELEMETRY_CTRL(2)

🎀 NAME 🎀

okay bestie, welcome to the libnvme API manual ✨ today's main character is nvme_get_log_telemetry_ctrl — she's here to Get Telemetry Controller-Initiated log page 💅

---

🦋 SYNOPSIS 🦋

int nvme_get_log_telemetry_ctrl (int fd , bool rae , __u64 offset ,
       __u32 len , void *log );

---

🌸 ARGUMENTS 🌸

• fd — the file descriptor of your nvme device 🫶 like, this is the doorway, okay?
• rae — Retain asynchronous events ✨ (yes queen, hold onto those events)
• offset — Offset into the telemetry data 📍 where you wanna start scooping from
• len — Length of provided user buffer to hold the log data in bytes 📏 that's the size of the lil container you're handing over
• log — User address for log page data 🎀 the spot where the log data is gonna land

---

💖 DESCRIPTION 💖

So here's the vibe: this function Retrieves the Telemetry Controller-Initiated log page at the requested offset using the previously existing capture 🔥 no cap, it's just pulling that log page for you at wherever you said, off the capture that was already there.

---

⭐ RETURN ⭐

It hands you back The nvme command status if a response was received (see enum nvme_status_field) 👑 or, if things went sideways, -1 with errno set otherwise 💀 (iykyk, always check that errno bestie)

---

and that's the whole page, fr fr 🌈 thanks for reading, mwah 💜

July 2026 — that's the date stamp, and this was the libnvme API manual, page nvme_get_log_telemetry_ctrl(2) 🎀 bye babe, go log something iconic ✨