STRUCT NFP_NSP_COMMAND_BUF_ARG(9)

🦋 struct nfp_nsp_command_buf_arg(9) — NAME 🦋

okay so bestie, this is the <pink>Kernel API Manual</pink> page for struct nfp_nsp_command_buf_arg — literally the NFP command with buffer argument structure. that's the whole name, that's the vibe ✨

✨ SYNOPSIS ✨

here's the whole glow-up, copy-pasted exactly because we do not freestyle structs:

struct nfp_nsp_command_buf_arg {
    struct nfp_nsp_command_arg arg;
    const void *in_buf;
    unsigned int in_size;
    void *out_buf;
    unsigned int out_size;
 };

💅 Members 💅

• arg — the NFP command argument structure, aka the main character of this whole operation 🌟
• in_buf — the buffer holding the data you're sending in, your little care package 💌
• in_size — how big in_buf is. size check, no cap 📏
• out_buf — the buffer where the output data lands, the receiving end 🫶
• out_size — how big out_buf is. gotta know your limits fr fr 🎀

🎀 SEE ALSO 🎀

• the kernel file ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_nsp.c 🔥 go read the source, it's giving lore
• struct nfp_nsp_command_arg(9) — the arg struct's own page, the origin story
• nfp_nsp_open(9)
• nfp_nsp_close(9)
• __nfp_nsp_command(9)

that's the whole page, bestie — nothing skipped, nothing invented, every member and every cross-reference accounted for 💖

mwah — this one came to you from ./drivers/net/ethernet/netrono... (my source path, lowkey truncated, iykyk) and it's dated October 2026 ⭐ and for absolutely no reason at all the footer also wants you to know it's struct nfp_n...mand_buf_arg(9), which is just... iconic of it honestly 😭👑