libnvme(9)
πΈ libnvme(9) β the API Manual, bestie edition πΈ
okay so real talk, this is a page straight outta libnvme(9), aka the API Manual, and it's tiny but it matters. It documents enum nvme_timestamp_attr, which is honestly giving "small but mighty" β the whole thing is about the Timestamp Attribute field. no cap. π
β¨ NAME β¨
enum nvme_timestamp_attr β the Timestamp Attribute field π
like, that's it, that's the whole vibe. it's the enum that holds the Timestamp Attribute field, and honestly? iconic.
π¦ SYNOPSIS π¦
enum nvme_timestamp_attr {
NVME_TIMESTAMP_ATTR_SYNC_SHIFT ,
NVME_TIMESTAMP_ATTR_TO_SHIFT ,
NVME_TIMESTAMP_ATTR_SYNC_MASK ,
NVME_TIMESTAMP_ATTR_TO_MASK
};
look at her. four constants, zero drama. copy it exactly, okay? character for character, no freestyling π
π§ Constants π§
okay so here's the breakdown of every single one β not skipping a single one, periodt:
NVME_TIMESTAMP_ATTR_SYNC_SHIFTβ the shift amount you use to get the timestamp synch. it's a shift, so you're shifting bits, iykyk. πNVME_TIMESTAMP_ATTR_TO_SHIFTβ the shift amount that gets you the timestamp origin. same deal, different field. βNVME_TIMESTAMP_ATTR_SYNC_MASKβ the mask to get the timestamp synch. masks are for isolating bits, and this one's serving main character energy. πNVME_TIMESTAMP_ATTR_TO_MASKβ the mask to get the timestamp origin. last one, and she ate. π
ngl bestie, shifts and masks sound similar but they are not the same thing β the*_SHIFTones are shift amounts, the*_MASKones are masks. do not mix them up, I'm begging π
π«Ά the cute sign-off π«Ά
and that's the whole page!! this little gem is from the libnvme API Manual, section 9, dated October 2026, and it's filed under enum nvme_timestamp_attr. slay. go forth and handle your timestamps responsibly πβ¨π
π¦ 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