nvme_submit_io_passthru64(2)
π nvme_submit_io_passthru64 π
okay so bestie, welcome to the libnvme API manual, section 2 girlypop edition β¨ this one is literally nvme_submit_io_passthru64 and she is here to submit a 64-bit nvme passthrough command. that's the whole name, that's the whole vibe, and yes the 64 is load-bearing π
πΈ SYNOPSIS πΈ
int nvme_submit_io_passthru64 (int fd , struct nvme_passthru_cmd64 *cmd
, __u64 *result );
like... three args, one int back. she's giving minimalism π
π ARGUMENTS π
fdβ the file descriptor of your nvme device, aka your backstage pass to the drive π«Άcmdβ the nvme io command you're sending, the actual moment, the main character of this whole operation π«resultβ an optional field that hands you back the result from the CQE DW0-1. optional bestie!! she can be skipped, no pressure π
π¦ DESCRIPTION π¦
under the hood this uses NVME_IOCTL_IO64_CMD for the ioctl request. that's it, that's the tea β no extra steps, no sneaky behaviour, just the one ioctl. iykyk π₯
β RETURN β
she gives you the nvme command status if a response came back (peep enum nvme_status_field for the deets on that), or -1 with errno set if things went sideways π so like, always check. always. fr fr.
not me reminding you to check for-1... but also literally check for-1π
and that's the page!! July 2026 energy, from the libnvme API manual, written with love and a lil bit of glitter πβ¨ mwah, go submit some passthrough commands responsibly πππ¦
π¦ 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