nvme_init_write(9)

nvme_init_write(9)

okay so this page comes from the libnvme API manual, and it's giving “small function, very specific job” energy. We're talking about nvme_init_write(9), bestie, and we are not skipping a single argument. 💅✨

💖 NAME 💖

nvme_init_write — Initialize passthru command for a user write command. That's the whole assignment: it does the setup for a user write command's passthru command. 🎀

✨ SYNOPSIS ✨

Here's the signature, exactly as it is — no edits, no cap:

void nvme_init_write (struct libnvme_passthru_cmd *cmd , __u32 nsid ,
       __u64 slba , __u16 nlb , __u16 control , __u16 dspec , __u8 dsm , __u8
       cev , void *data , __u32 data_len , void *metadata , __u32 metadata_len
       );

🎀 ARGUMENTS 🎀

Every arg, in order, zero skips:

• cmd — the passthru command you're using. This is the thing getting set up. 🫶
• nsid — Namespace ID, periodt.
• slba — Starting logical block.
• nlb — Number of logical blocks, and yes bestie, it's 0-based. Don't forget the 0.
• control — Upper 16 bits of cdw12. That's the exact slice. ✨
• dspec — Directive specific value.
• dsm — Data set management attributes, specifically for the CETYPE-is-zero situation; see enum nvme_io_dsm_flags. 👀
• cev — Command Extension Value, for the CETYPE-is-non-zero situation.
• data — Pointer to user address of the data buffer.
• data_len — Length of user buffer, data, in bytes.
• metadata — Pointer to user address of the metadata buffer.
• metadata_len — Length of user buffer, metadata, in bytes.

🦋 DESCRIPTION 🦋

Initializes the passthru command buffer for the Write command. That's it, that's the whole job — it sets up the passthru command buffer for the Write command, and then it's done. No extra lore, no secret side quests. 💜

Source/version and date check, because we do not skip footers: this page is from the libnvme API manual, dated October 2026, and the function/page name is nvme_init_write / nvme_init_write(9). Bye bestie, go init that write! 🫶💖🎀