qed_ll2_set...of_tx_packet(9)

📦 version 7.3.1, in nixpkgs unstable

💅 qed_ll2_set_fragment_of_tx_packet 💅

okay so this is a page from the Kernel API Manual (yes, the actual kernel man pages, we're in the big leagues now bestie) and it's all about qed_ll2_set_fragment_of_tx_packet 🦋

✨ NAME ✨

qed_ll2_set_fragment_of_tx_packet — it's the girl that provides fragments to fill Tx BD of the BDs that were requested by qed_ll2_prepare_tx_packet 🎀

like, you know how qed_ll2_prepare_tx_packet puts in the request for BDs? this is the follow-up queen that actually hands over the fragments to fill them. iconic teamwork fr fr 💖

🌸 SYNOPSIS 🌸

int qed_ll2_set_fragment_of_tx_packet (void *cxt , u8 connection_handle
, dma_addr_t addr , u16 nbytes );

that's the whole vibe check right there ⭐

🫶 ARGUMENTS 🫶

  • cxt — Pointer to the hw-function [opaque to some]. 👑 so it's a hardware function pointer situation, and some of us (me, you, everyone) just aren't meant to see inside it. it's giving mystery. it's giving "don't worry about it."
  • connection_handle — the LL2 connection's handle, and you get it from qed_ll2_require_connection. that's the whole source of truth for this one, no cap 💀
  • addr — Address. 🎀 that's it. that's the description. address.
  • nbytes — Number of bytes. 🌸 short and sweet and to the point, love that for it.

🔥 RETURN 🔥

  • 0 on success ✨
  • failure otherwise 😭

that's the whole deal. 0 means we slayed, anything else means we did not slay.

lowkey a real one for keeping the return values this simple. main character energy 💜

🌈 SEE ALSO 🌈

okay the reading list, let's go:

basically the entire qed_ll2 friend group 💅 they all show up together, as they should.

mwah 💋 that's a wrap bestie — this page lives in ./drivers/net/ethernet/qlogic/qed, it's dated October 2026, and it's filed under the Kernel API Manual. go forth and fragment responsibly 🧚‍♀️💖

📦 where this page comes from