libnvme(9)
π libnvme(9) β API Manual π
okay bestie, welcome to the libnvme API manual, section 9 π this one's a lil struct deep-dive and honestly it's giving "I have a very specific job and I do it flawlessly" energy β¨
β¨ NAME β¨
struct nvme_zns_mgmt_recv_args β the arguments for the NVMe ZNS Management Receive command π¦
no cap, that's literally the whole vibe. it's the lil bag of stuff you hand over when you wanna do a ZNS management receive.
πΈ SYNOPSIS πΈ
struct nvme_zns_mgmt_recv_args {
__u64 slba;
__u32 *result;
void *data;
int args_size;
int fd;
__u32 timeout;
__u32 nsid;
enum nvme_zns_recv_action zra;
__u32 data_len;
__u16 zrasf;
bool zras_feat;
};
look at her. eleven members. all accounted for. iconic. π
π Members π
one bullet per member, and yes we're doing all of them, because skipping members is not the move π
slbaβ the Starting logical block address. where the party starts πresultβ the command completion result, straight outta CQE dword0 π―dataβ the userspace address of the data. yes bestie, your buffer lives here πargs_sizeβ the size ofstruct nvme_zns_mgmt_recv_args. she knows her own measurements, self-aware queen πfdβ the file descriptor of the nvme device πtimeoutβ timeout in ms β³ (milliseconds, fr fr)nsidβ Namespace ID πͺͺzraβ zone receive action πdata_lenβ length of data πzrasfβ Zone receive action specific field πzras_featβ Zone receive action specific features β¨
ngl bestie, if you're passing this struct around, double-check args_size matches what you think it is β she's the one telling everyone how big the struct is, and she does not want to be wrong about it π
and that's the whole page, we ate and left no crumbs π
this was struct nvme_zns_mgmt_recv_args, from the libnvme(9) API Manual, dated August 2026 π
bye bestie, go receive some zones, mwah ππ
π¦ where this page comes from
- fedora 44: libnvme-doc 1.16.2-1.fc44 Β· 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