NVME_GET_LOG_ENDURANCE_GRP_EVT(2)
β¨ nvme_get_log_endurance_grp_evt(2) β¨
okay bestie, so this one lives in the libnvme API manual, and the function we're hyping up today is nvme_get_log_endurance_grp_evt β say that five times fast, I dare you π
π NAME π
nvme_get_log_endurance_grp_evt β go get that Endurance Group Event Aggregate π
π¦ SYNOPSIS π¦
int nvme_get_log_endurance_grp_evt (int fd , bool rae , __u32 offset ,
__u32 len , void *log );
πΈ ARGUMENTS πΈ
fdβ the file descriptor of the nvme device. like, your little handle to the drive itself bestie π«Άraeβ Retain asynchronous events. flip this and the events stay put instead of ghosting youoffsetβ where in the log page you wanna start reading from. offset to the start of the log page, periodtlenβ how much space you've got allocated for the log page. the allocated length, no caplogβ the user address where the log page gets stored. hand it a buffer and it'll fill it up π
π₯ RETURN π₯
If a response actually came back, you get the nvme command status β peek at enum nvme_status_field for the deets. If not? it's -1 with errno set. rude, but that's the deal π
ngl bestie, always check the return value. -1 is not the vibe you want to see at 3am.
and that's the whole page, you ate that π stay iconic, keep your buffers big enough, and remember: this is the libnvme API manual, dated July 2026 β written for the girlies who read manpages for fun πβ¨π¦
π¦ where this page comes from
- ubuntu stonking: libnvme-dev 1.16.2-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms