LIBNVME_PATH_GET_WRITE_TICKS-LIBNVME3(2)
π¦ libnvme_path_get_write_ticks(9) β the write-ticks one π¦
okay bestie, real talk: this page is from the libnvme API manual, section 9, and it's a teeny tiny one β but it's lowkey important so let's not sleep on it π
β¨ NAME β¨
libnvme_path_get_write_ticks β bestie, this one gets the write I/O ticks. that's the whole job. iconic, honestly π
β¨ SYNOPSIS β¨
unsigned int libnvme_path_get_write_ticks (struct libnvme_path *p );
yes that's it, one function, one pointer, no cap π«Ά
β¨ ARGUMENTS β¨
pβ astruct libnvme_pathobject. that's your path bestie, she's the main character here π
β¨ RETURN β¨
so when this returns, you get the time, in milliseconds, that was spent processing write I/O requests between two stat samples β±οΈβ¨
literally just: milliseconds, write I/O, between two stat samples. iykyk πΈ
π quick vibe check: the unit is milliseconds, not seconds, not nanoseconds. don't do that to yourself.
and that's the whole page, bestie β short, sweet, and she ate π this one's from the libnvme API manual, dated October 2026, published under the libnvme name β mwah, see u in the next manpage ππ§ββοΈ
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms