idpf_tx_spli...et_free_bufs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… idpf_tx_spli...et_free_bufs(9) β€” bestie's guide to the Kernel API Manual ✨

okay so real talk, the header is idpf_tx_spli...et_free_bufs(9) (yes the name is literally abbreviated with dots, that's the whole vibe, it's giving "the kernel couldn't fit the whole thing in the tab title") and this page lives in the Kernel API Manual. she's short, she's sweet, she's a u32-returning icon. let's get into it 🫢


🌸 NAME 🌸

idpf_tx_splitq_get_free_bufs β€” literally just get number of free buf_ids in refillq. that's it. that's the whole job. no cap. πŸ’…


✨ SYNOPSIS ✨

u32 idpf_tx_splitq_get_free_bufs (struct idpf_sw_queue *refillq );

she takes one (1) pointer and hands you back a u32. simple. elegant. iconic. keep the spacing exactly like that, code is code, we don't touch code. πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • refillq β€” pointer to the refillq that's holding the buf_ids. that's the whole argument, bestie, one pointer, main character energy only πŸ’–

πŸ¦‹ SEE ALSO πŸ¦‹

okay this is the part where the manpage flexes its friend group. like, she knows everyone in ./drivers/net/ethernet/intel/idpf/idpf_txrx.h. the whole squad, no gatekeeping:

  • struct idpf_tx_offload_params(9) 🌈
  • struct idpf_tx_splitq_params(9)
  • enum idpf_queue_flags_t(9)
  • struct idpf_vec_regs(9)
  • struct idpf_intr_reg(9)
  • struct idpf_q_vector(9)
  • struct idpf_rx_queue(9)
  • struct idpf_tx_queue(9)
  • struct idpf_buf_queue(9)
  • struct idpf_compl_queue(9)
  • struct idpf_sw_queue(9) πŸ‘‘ (yes bestie, the one from the arguments, we see you)
  • struct idpf_rxq_set(9)
  • struct idpf_bufq_set(9)
  • struct idpf_rxq_group(9)
  • struct idpf_txq_group(9)
  • idpf_size_to_txd_count(9)
  • idpf_tx_singleq_build_ctob(9)
  • idpf_tx_splitq_build_desc(9)
  • idpf_vport_intr_set_wb_on_itr(9) ⭐

and yeah she's from the Kernel file ./drivers/net/ethernet/intel/idpf/idpf_txrx.h β€” that's the address, don't @ me 🐝


lowkey a reminder from your girl: this page gives you the what, not the how β€” the refillq pointer is what you pass in, u32 is what you get back, and the SEE ALSO list is where you go when you need actual context. iykyk πŸ’œ

and that's the whole page, bestie!! no crumbs left, we kept every single detail πŸ“ this lil cutie comes straight from ./drivers/net/ethernet/intel/idpf, dated October 2026, catalogued under idpf_tx_spli...et_free_bufs(9) β€” periodt, slay, go call your free buf_ids πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from