libnvme(2)
π NAME π
okay bestie, gather round β this page lives in the libnvme(2) API Manual, and what it's giving you is:
enum nvme_io_opcode β the Opcodes for I/O Commands
that's it, that's the whole vibe: one enum, twenty members, zero chill. it's the master list of every I/O command opcode nvme knows about, and we're gonna go through every single one together, no skipping, no scrolling past. π«Ά
π¦ SYNOPSIS π¦
here's the whole thing in its natural habitat, copy-paste ready, not a single member changed:
enum nvme_io_opcode {
nvme_cmd_flush ,
nvme_cmd_write ,
nvme_cmd_read ,
nvme_cmd_write_uncor ,
nvme_cmd_compare ,
nvme_cmd_write_zeroes ,
nvme_cmd_dsm ,
nvme_cmd_verify ,
nvme_cmd_resv_register ,
nvme_cmd_resv_report ,
nvme_cmd_resv_acquire ,
nvme_cmd_io_mgmt_recv ,
nvme_cmd_resv_release ,
nvme_cmd_cancel ,
nvme_cmd_copy ,
nvme_cmd_io_mgmt_send ,
nvme_zns_cmd_mgmt_send ,
nvme_zns_cmd_mgmt_recv ,
nvme_zns_cmd_append ,
nvme_cmd_fabric
};
yes, there's a lil blank line before the closing brace, and yes, we're keeping it. character for character, bestie. π the way that last blank line is just sitting there is honestly so real of it.
β¨ Constants β¨
and now the moment you've all been waiting for β the official roll call. twenty members, in order, with what each one is called. π
nvme_cmd_flushβ Flush πnvme_cmd_writeβ Write βοΈnvme_cmd_readβ Read πnvme_cmd_write_uncorβ Write Uncorrectable π₯nvme_cmd_compareβ Compare βοΈnvme_cmd_write_zeroesβ write Zeros π«₯ (the page genuinely writes it lowercase as "write Zeros" and we are NOT fixing it, we're respecting the author's choices)nvme_cmd_dsmβ Dataset Management ποΈnvme_cmd_verifyβ Verify βnvme_cmd_resv_registerβ Reservation Register πnvme_cmd_resv_reportβ Reservation Report πnvme_cmd_resv_acquireβ Reservation Acquire πnvme_cmd_io_mgmt_recvβ I/O Management Receive π₯nvme_cmd_resv_releaseβ Reservation Release πnvme_cmd_cancelβ Cancel π«nvme_cmd_copyβ Copy πnvme_cmd_io_mgmt_sendβ I/O Management Send π€nvme_zns_cmd_mgmt_sendβ Zone Management Send π§nvme_zns_cmd_mgmt_recvβ Zone Management Receive π§nvme_zns_cmd_appendβ Zone Append βnvme_cmd_fabricβ Fabric Commands π§΅
heads up bestie: that's all the information this page gives you. no defaults, no return values, no error codes, no signals, no environment variables, no SEE ALSO β just the enum and these descriptions. so don't go inventing behaviour for any of these bad boys. if you need the actual semantics, that's a different page's problem. π
also notice the naming switch-up, iykyk: the first chunk is all nvme_cmd_*, and then four of them β nvme_zns_cmd_mgmt_send, nvme_zns_cmd_mgmt_recv, nvme_zns_cmd_append β come in as nvme_zns_cmd_* instead, then nvme_cmd_fabric brings us right back home. the way it just switches prefixes mid-enum like that? main character energy. periodt. π
and that's the whole page, gorgeous. π twenty opcodes, fully accounted for, nothing skipped, nothing invented, vibe check passed with flying colours. go forth and reference your enum members responsibly. π
this has been enum nvme_io_opcode from the libnvme(2) manual β dated July 2026, which is literally so futuristic of it β signing off, mwah, slay, eat your veggies, #include your headers. πΈπ«Άβ
π¦ 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