qed_get_igu...lts_buf_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

qed_get_igu_fifo_results_buf_size β€” bestie, this one tells you the buffer size you need for igu_fifo results (in bytes, okay, we're measuring in bytes here ✨)

So real talk, manual name is qed_get_igu...lts_buf_size(9) from the Kernel API Manual β€” the whole thing is like a lil window into the qed debug world 🫢


✨ SYNOPSIS ✨

enum dbg_status qed_get_igu_fifo_results_buf_size (struct qed_hwfn
*p_hwfn , u32 *dump_buf , u32 num_dumped_dwords , u32 *results_buf_size
);

That's the whole signature, no cap πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • p_hwfn β€” HW device data. literally the hardware's whole vibe holder, okay 😌
  • dump_buf β€” IGU fifo dump buffer. the actual dump goes in here πŸ—‘οΈβœ¨
  • num_dumped_dwords β€” number of dwords that were dumped. count those dwords bestie, every single one πŸ”’
  • results_buf_size β€” (OUT) required buffer size (in bytes) for the parsed results. it's an OUT param so this is where the answer comes back out to you, iconic πŸ’…

πŸ”₯ RETURN πŸ”₯

Error if the parsing fails, ok otherwise. that's it, that's the whole vibe check β€” parse fails = error, everything else = ok πŸ™ˆπŸ¦‹


🌸 SEE ALSO 🌸

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_dbg_hsi.h

like, that's the whole friend group right there, everybody showed up to the function party πŸ‘‘πŸ’œ


ok and this page lives in ./drivers/net/ethernet/qlogic/qed and it's dated October 2026 β€” slay, mark your calendars bestie πŸ—“οΈπŸ’– mwah, bye! 🌈✨
πŸ“¦ where this page comes from