nvme_init_verify(9)

📦 version 3.2, in arch rolling

💅 nvme_init_verify(9) 💅

okay bestie, welcome to the libnvme API manual — this is the page for nvme_init_verify, and honestly? it's giving "small function, big job." let's get into it 🎀

✨ NAME ✨

nvme_init_verify — initialize the passthru command for a verify command 🦋

🌸 SYNOPSIS 🌸

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

like, yes, that's ten (10) whole arguments. she's high maintenance but she's worth it 💅

🫶 ARGUMENTS 🫶

  • cmd — the passthru command you're setting up. this is the main character, everything gets written into it ✨
  • nsid — Namespace ID. which namespace we're talking to 🗂️
  • slba — starting logical block. where the party begins 🔥
  • nlb — number of logical blocks — and heads up, it's 0-based, so don't come at it with your 1-based brain 🙈
  • control — the upper 16 bits of cdw12. yes, just the upper half, don't get greedy 💀
  • cev — Command Extension Value (CETYPE is non-zero, iykyk) 💖
  • data — pointer to the user address of the data buffer 🧚
  • data_len — length of the user buffer, data, in bytes 📏
  • metadata — pointer to the user address of the metadata buffer 🌈
  • metadata_len — length of the user buffer, metadata, in bytes 📏

👑 DESCRIPTION 👑

so what does it actually do? it initializes the passthru command buffer for the Verify command. that's it, that's the vibe. clean, simple, iconic ⭐

💀 NOTE 💀

okay this part matters, bestie, don't skip it: the Verify command transfers data or metadata to the controller to perform the verification, but not back to the host. so no data comes home. it's a one-way trip fr fr 😭

🍓 sign-off 🍓

that's the whole page, bestie — brought to you by libnvme API manual, version nvme_init_verify, dated October 2026. slay, go verify something 💜✨

📦 where this page comes from