i40e_disallo...hing_filters(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i40e_disallow_matching_filters β€” Kernel API Manual, section 9

okay so bestie, welcome to the manual page for i40e_disallow_matching_filters, straight out of the Kernel API Manual (yes, section 9, the ~fancy~ one). grab a lil snack, we're checking filters together πŸ“


✨ NAME ✨

i40e_disallow_matching_filters β€” literally just checking that your new filters differ from the ones already chilling in there πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int i40e_disallow_matching_filters (struct i40e_vsi *vsi , struct
i40e_fdir_filter *input );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • vsi β€” pointer to the targeted VSI, aka the vibe we're aiming at 🎯
  • input β€” the new filter we're about to check, no cap

🌸 DESCRIPTION 🌸

so here's the tea, bestie: due to hardware limitations, it is not possible for two filters that match similar criteria to be programmed at the same time. and like, it's true for a few reasons:

  • (a) all filters matching a particular flow type must use the same input set, that is they must match the same criteria.
  • (b) different flow types will never match the same packet, as the flow type is decided by hardware before checking which rules apply.
  • (c) hardware has no way to distinguish which order filters apply in. πŸ’€

due to this, we can't really support using the location data to order filters in the hardware parsing. it is technically possible for the user to request two filters matching the same criteria but which select different queues. in this case, rather than keep both filters in the list, we reject the 2nd filter when the user requests adding it. πŸ™ˆ

this avoids needing to track location for programming the filter to hardware, and ensures that we avoid some strange scenarios involving deleting filters which match the same criteria. iconic behaviour honestly πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

like, the whole i40e extended family shows up here, iykyk:


bestie reminder: two filters matching the same criteria at the same time? not happening. hardware said no and we respect the boundary 🫢

that's the whole page, mwah πŸ’– this one lives in ./drivers/net/ethernet/intel/i40e and it's dated October 2026 β€” go off, driver directory, you ate ⭐🌈

πŸ“¦ where this page comes from