libnvme(2)
π NAME π
enum nvme_io_control_flags β bestie, it's the I/O control flags, and they're literally the little toggles that tell your NVMe I/O how to behave β¨
π¦ SYNOPSIS π¦
okay so the whole enum, verbatim, no cap:
enum nvme_io_control_flags {
NVME_IO_DTYPE_STREAMS ,
NVME_IO_NSZ ,
NVME_IO_STC ,
NVME_IO_DEAC ,
NVME_IO_ZNS_APPEND_PIREMAP ,
NVME_IO_PRINFO_PRCHK_REF ,
NVME_IO_PRINFO_PRCHK_APP ,
NVME_IO_PRINFO_PRCHK_GUARD ,
NVME_IO_PRINFO_PRACT ,
NVME_IO_FUA ,
NVME_IO_LR
};
πΈ Constants πΈ
eleven of them, she's serving a full menu, let's get into it π
NVME_IO_DTYPE_STREAMSβ Directive Type Streams. streams, but make it a directive type πNVME_IO_NSZβ Namespace Zeroes. the namespace? zeroed. iconic.NVME_IO_STCβ Storage Tag Check. checking the storage tag, as one does β¨NVME_IO_DEACβ Deallocate. bye bye blocks, we're deallocating π«ΆNVME_IO_ZNS_APPEND_PIREMAPβ Protection Information Remap. PI remap energy, zns append edition πNVME_IO_PRINFO_PRCHK_REFβ Protection Information Check Reference Tag. checking that reference tag fr frNVME_IO_PRINFO_PRCHK_APPβ Protection Information Check Application Tag. and now checking the application tag, she's thorough πNVME_IO_PRINFO_PRCHK_GUARDβ Protection Information Check Guard field. the guard field gets checked too, no one is left out πNVME_IO_PRINFO_PRACTβ Protection Information Action. it's giving action, not just checks πNVME_IO_FUAβ Force Unit Access. FUA! forcing that unit access, main character move π₯NVME_IO_LRβ Limited Retry. retries, but limited. she knows her limits π§
ngl bestie, that's the whole page β every constant, every tag, every check, exactly as the manual says it π
and a lil sign-off for u: this was enum nvme_io_control_flags from the API Manual, dated July 2026, living under libnvme(2) β slay, periodt, go forth and set your I/O control flags π
π¦ 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