wx_setup_all_tx_resources(9)

📦 version 7.3.1, in nixpkgs unstable

✨ wx_setup_all_tx_resources ✨

okay so bestie, welcome to the Linux Kernel API Manual page for wx_setup_all_tx_resources — section 9, kernel API vibes only, no cap 💅

🌸 NAME 🌸

wx_setup_all_tx_resources — the girl who allocates all the queues' Tx resources 🎀

🦋 SYNOPSIS 🦋

int wx_setup_all_tx_resources (struct wx *wx );

💜 ARGUMENTS 💜

  • wx — pointer to the private structure 👑 (that's the whole vibe, it's just a pointer to the private struct)

🔥 DESCRIPTION 🔥

okay so listen, this is the important bit and I need you to hear me 🙈

If this function returns with an error, then it's possible that one or more of the rings is populated (while the rest are not). literally a partial-slay situation. And it is the caller's duty to clean those orphaned rings — that's on you, bestie, not on this function. you adopted them, you clean them 🫶

It returns 0 on success, and a negative value on failure. periodt.

⚠️ lowkey the main character energy here is "returns error → some rings are still full → you gotta clean up." do not skip that part fr fr

👑 SEE ALSO 👑

Kernel file ./drivers/net/ethernet/wangxun/libwx/wx_lib.c — that's the source of truth, iykyk 💖

and here's the whole friend group, like every single one of them, no one left out 🥹:

🧚 tiny sign-off before you go: this page lives under ./drivers/net/ethernet/wangxun... and it's dated October 2026, and yes it's still called wx_setup_all_tx_resources(9) — slay, go allocate something 🌈⭐💀
📦 where this page comes from