NVME_INIT_MANAGE_EXPORT_NVMS_RECEIVE-LIBNVME3(2)
π NAME π
nvme_init_manage_export_nvms_receive β bestie, this is the one that initializes the passthru command for Manage Exported NVM Subsystem Receive β¨ and like, that's literally the whole vibe of it.
This page lives in the libnvme API manual, section 9, and it's giving "fancy kernel-adjacent documentation but make it cute" π
πΈ SYNOPSIS πΈ
void nvme_init_manage_export_nvms_receive (struct libnvme_passthru_cmd
*cmd , __u8 sel , __u8 mos , __u16 mose , __u16 mosi , __u32 ol , __u32
ou , __u32 numdl , void *data , __u32 len );
okay so it returns void β nothing comes back, it just does the thing π
and it takes a whole lil friend group of arguments, which we are gonna go through one by one, no skipping, periodt.
π¦ ARGUMENTS π¦
cmdβ the passthru command you're gonna use. This is the main character fr, everything gets written into it π«Άselβ Select (SEL): the management operation you wanna perform. go look atenum nvme_manage_export_nvms_recv_selfor the list, iykyk πmosβ Management Operation Specific (MOS): this one's specific toselmoseβ Management Operation Specific Extended (MOSE): also specific tosel, yes it's a whole extended moment π«mosiβ Management Operation Specific Identifier (MOSI): once again, specific toselolβ Offset Lower (OL), in dwords: specific tosel. lowercaseol, lowercase keys, we love a consistent queen πouβ Offset Upper (OU), in dwords: specific tosel. the upper half of the offset situation, slay βnumdlβ Number of Dwords (NUMDL) requested, 0's based: specific tosel. yes bestie, zero-based, do not forget, that's an off-by-one waiting to humble you πdataβ pointer to the data buffer. this is where the actual payload hangs out πΈlenβ length of the data. gotta know how much data you're data-ing, fr fr
lowkey notice howmos,mose,mosi,ol,ou, andnumdlare all "specific tosel"? yeah.selis the main character here and everyone else is just following her lead π
π DESCRIPTION π
It initializes the passthru command buffer for the Manage Exported NVM Subsystem Receive command.
That's it. That's the whole job. It sets up the buffer, hands it back through cmd, and you take it from there, bestie π
and that's a wrap on the libnvme API manual entry for nvme_init_manage_export_nvms_receive, section 9, dated October 2026 πΈ go forth and initialize your passthru commands, you iconic thing, you πβ¨
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms