nvme_init_copy_range_f1(9)

📦 version 3.2, in arch rolling

💅 nvme_init_copy_range_f1(9) — a libnvme API manual moment

okay bestie, welcome to the libnvme API manual, page for nvme_init_copy_range_f1 🎀 — yes that's a whole mouthful, yes it's iconic, and yes we're gonna get through it together.

✨ NAME ✨

nvme_init_copy_range_f1 — constructs a copy range f1 structure 🦋

like, literally it builds you the structure. that's the whole job. and it slays at it.

🌸 SYNOPSIS 🌸

void nvme_init_copy_range_f1 (struct nvme_copy_range_f1 *copy , __u16
*nlbs , __u64 *slbas , __u64 *eilbrts , __u16 *elbatms , __u16 *elbats ,
__u16 nr );

no cap, that's seven (7) things going in and nothing coming out — void return, we love a function that just does the thing and leaves 💅

💖 ARGUMENTS 💖

  • copy — the copy range array 🫶 this is the main character, the thing being filled in
  • nlbs — number of logical blocks, aka how many lblocks bestie 🔥
  • slbas — starting LBA, the spot where it all begins ⭐
  • eilbrts — expected initial logical block reference tag, say that five times fast 😭
  • elbatms — expected logical block application tag mask (it's the mask one, don't mix it up with the next one 🙈)
  • elbats — expected logical block application tag, no mask, just tag 🎀
  • nr — number of descriptors to construct — how many you wanna build, you tell it, it builds 👑
lowkey note: elbatms and elbats differ by exactly one letter and they're both __u16 *, so like… vibe check your variable names before you call this, bestie. iykyk 💀

🧚 a lil sign-off 🧚

this page is nvme_init_copy_range_f1(9) from the libnvme API manual, dated October 2026 — go forth and construct those copy range f1 structures, you absolute icon 💜✨🌸

📦 where this page comes from