STRUCT ETHNL_DUMP_CTX(9)

💅 STRUCT ETHNL_DUMP_CTX(9) 💅

okay bestie, welcome to the Kernel API Manual — you're literally about to meet struct ethnl_dump_ctx, no big deal, just the moment our whole friendship levels up 🫶

---

🌸 NAME 🌸

struct ethnl_dump_ctx — the context structure for the generic dumpit() callback. that's it, that's the vibe 💖

---

✨ SYNOPSIS ✨

struct ethnl_dump_ctx {
    const struct ethnl_request_ops  *ops;
    struct ethnl_req_info           *req_info;
    struct ethnl_reply_data         *reply_data;
    unsigned long                   pos_ifindex;
 };

ngl, look at those four members. absolute main character energy. read on, queen 👑

---

🎀 MEMBERS 🎀

• ops — the request ops of the message type that's currently being processed. like, whose turn is it? this tells you 💅
• req_info — the parsed request header of the request being processed. the receipts, essentially 🙈
• reply_data — the data needed to compose the reply. everything you need to clap back, all in one place ✨
• pos_ifindex — the saved iteration position — ifindex. yes, the position is saved, we don't lose our place, that's just polite 💜

---

🦋 DESCRIPTION 🦋

so these parameters are kept inside struct netlink_callback as context preserved between iterations. like, the struct remembers stuff so you don't have to 😭 iconic behaviour fr fr.

they get initialized by ethnl_default_start, and then used in ethnl_default_dumpit and ethnl_default_done. that's the whole little lifecycle — start, dumpit, done. the way that this manpage just tells you the plot 🍓

---

🔥 SEE ALSO 🔥

the Kernel file ./net/ethtool/netlink.c — plus these absolute legends:

• ethnl_parse_header_dev_get(9)
• ethnl_fill_reply_header(9)
• ethnl_reply_init(9)
• struct ethnl_perphy_dump_ctx(9)
• ethnl_default_parse(9)
• ethnl_init_reply_data(9)

iykyk, go read them, they're all slay 💀✨

---

and that's the page!! this little cutie lives in ./net/ethtool, and it was dated October 2026, periodt. go off and dump some contexts bestie, you've got this 💅👑🌈