iavf_get_rxfh(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– iavf_get_rxfh(9) β€” the Kernel API Manual glow-up πŸŽ€

okay so bestie, welcome to the iavf_get_rxfh page from the Kernel API Manual ✨ this one is short and sweet and honestly kind of a vibe. grab a strawberry πŸ“ and let's go.


✨ NAME ✨

iavf_get_rxfh β€” get the rx flow hash indirection table πŸ‘‘

lowkey the whole personality of this function is right there in the name. it gets the indirection table. that's it. that's the gig. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int iavf_get_rxfh (struct net_device *netdev , struct ethtool_rxfh_param
*rxfh );

yes the signature is literally that. copy it exactly, do not "improve" it, do not reformat it, we do not do that here πŸ™ˆ


🌸 ARGUMENTS 🌸

  • netdev β€” the network interface device structure, aka the whole entire device you're asking about 🫢 this is the main character of the call, ngl.
  • rxfh β€” a pointer to the param struct, and inside it lives indir, key, and hfunc πŸ’« those three are the ones you care about here, iykyk.

🧚 DESCRIPTION 🧚

so what does it do? it reads the indirection table directly from the hardware. like, no middleman, no caching arc, straight to the silicon πŸ”₯ the way that it just goes and asks the hardware itself is honestly iconic.

no cap, that's the full description. short king behavior πŸ‘‘ it does one thing and it does it well.


⭐ RETURN ⭐

returns 0. always. fr fr. zero. every time. no error path, no drama, no plot twist πŸ’€ it is not giving "might fail" energy, it is giving "I always come back with 0" energy ✨


🌈 SEE ALSO 🌈

bestie there are SO many siblings, this family is huge 😭 but we're listing every single one because we don't skip anyone in this group chat:

Kernel file ./drivers/net/ethernet/intel/iavf/iavf_ethtool.c β€” and then:

struct iavf_stats(9), iavf_add_one_ethtool_stat(9), __iavf_add_ethtool_stats(9), iavf_add_ethtool_stats(9), iavf_add_queue_stats(9), __iavf_add_stat_strings(9), iavf_add_stat_strings(9), iavf_get_link_ksettings(9), iavf_get_sset_count(9), iavf_get_ethtool_stats(9), iavf_get_stat_strings(9), iavf_get_strings(9), iavf_get_msglevel(9), iavf_set_msglevel(9), iavf_get_drvinfo(9), iavf_get_ringparam(9), iavf_set_ringparam(9), __iavf_get_coalesce(9), iavf_get_coalesce(9), iavf_get_per_queue_coalesce(9), iavf_set_itr_per_queue(9), __iavf_set_coalesce(9), iavf_set_coalesce(9), iavf_set_per_queue_coalesce(9), iavf_fltr_to_ethtool_flow(9), iavf_ethtool_flow_to_fltr(9), iavf_is_mask_valid(9), iavf_parse_rx_flow_user_data(9), iavf_fill_rx_flow_ext_data(9), iavf_get_ethtool_fdir_entry(9), iavf_get_fdir_fltr_ids(9), iavf_add_fdir_fltr_info(9), iavf_add_fdir_ethtool(9), iavf_del_fdir_ethtool(9), iavf_set_rxnfc(9), iavf_get_rx_ring_count(9), iavf_get_rxnfc(9), iavf_get_channels(9), iavf_set_channels(9), iavf_get_rxfh_key_size(9), iavf_get_rxfh_indir_size(9), iavf_set_rxfh(9), iavf_set_ethtool_ops(9)

like I said. HUGE family. ate πŸ’…


πŸ’œ little reminder bestie: 0 always is a promise, not a suggestion. don't go writing error handling for a return value that is literally never anything else. that's not the vibe check we're passing today 🧚

and that's the page!! 🌸 this one came out of ./drivers/net/ethernet/intel/iavf, dated October 2026, from the Kernel API Manual (that's the iavf_get_rxfh(9) manual, section 9, mwah πŸ’‹). slay, go read the source, ily, bye πŸ«Άβœ¨πŸŽ€

πŸ“¦ where this page comes from