ice_arfs_cmp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_arfs_cmp(9) — a Kernel API Manual moment

okay so bestie, welcome to ice_arfs_cmp, straight out of the Kernel API Manual and honestly? she's a little icon. ✨

✨ NAME ✨

ice_arfs_cmp — checks whether an aRFS filter actually matches this flow. that's it, that's the whole job 🎀

🌸 SYNOPSIS 🌸

bool ice_arfs_cmp (const struct ice_fdir_fltr *fltr_info , const struct
       flow_keys *fk , __be16 n_proto , u8 ip_proto );

like, yes, she returns a bool, and yes, she takes four whole arguments. main character energy fr fr 💜

🦋 ARGUMENTS 🦋

  • fltr_info — the filter info of the saved ARFS entry. this is the receipt of what we already stashed away 🧾
  • fk — the flow dissector keys. the vibe check data, basically.
  • n_proto — has to be one of htons(ETH_P_IP) or htons(ETH_P_IPV6). no other options, bestie, it's giving "choose from the dropdown" 🔥
  • ip_proto — one of IPPROTO_TCP or IPPROTO_UDP. same deal, pick one of the two 💅

⭐ DESCRIPTION ⭐

so here's the tea: this function straight up assumes that n_proto and ip_proto are locked to those limited values. because of that, she is meant to be called only from ice_rx_flow_steer. like, she's not an open-invite girlie — she's got a very specific guest list 🎀

ngl, don't go calling her from random places. the assumption about n_proto and ip_proto is baked right in 🙈

👑 RETURN 👑

  1. true — fltr_info refers to the same flow as fk. they're matching. soulmates, even 💖
  2. false — fltr_info and fk refer to different flows. not the same flow, not the same vibe, moving on 💀

🌈 SEE ALSO 🌈

the kernel file herself: ./drivers/net/ethernet/intel/ice/ice_arfs.c

and the whole friend group:

that's the whole page, bestie 🫶 huge shoutout to ./drivers/net/ethernet/intel/ice and the October 2026 era of the Kernel API Manual for bringing us ice_arfs_cmp(9). slay, periodt, and remember: limited values only 💅✨

📦 where this page comes from