ice_vc_fdir_comp_rules(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_vc_fdir_comp_rules β€” bestie's guide to the kernel API manual

okay so first things first, the title is ice_vc_fdir_comp_rules(9), and this whole thing lives in the Kernel API Manual. That (9) is giving "kernel internals section, not for the faint of heart" energy and honestly? iconic.


✨ NAME ✨

ice_vc_fdir_comp_rules β€” literally just compares two filter rules to see if they have the same value 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

bool ice_vc_fdir_comp_rules (struct virtchnl_fdir_fltr_conf *conf_a ,
struct virtchnl_fdir_fltr_conf *conf_b );

no cap, that's the whole signature. two pointers in, one bool out. the way that it's so simple?? obsessed.


πŸŽ€ ARGUMENTS πŸŽ€

  • conf_a β€” the FDIR configuration for filter a
  • conf_b β€” the FDIR configuration for filter b

like, it's literally in the names bestie 😭 a and b, the OGs.


🌸 RETURN 🌸

0 on success, and other on error. yes, "other" β€” that's what the manual says, so that's what you get πŸ’€

ngl, if you were hoping for a detailed breakdown of what each nonzero value means, this page is not gonna feed you. 0 = success, anything else = not success. periodt.

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is LONG and every single one of these has main character energy, so buckle up 🎒

like I said β€” every single one, no skips, no "etc." energy. iykyk πŸ’…


and that's the page!! πŸŽ€ source/version situation is ./drivers/net/ethernet/intel/i... and the date on this cutie is October 2026, so mark your calendars bestie. stay slay, go compare some filter rules, and remember: if it's not a 0 return, it's giving error πŸ’–βœ¨

πŸ“¦ where this page comes from