ice_flow_add_fld_raw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

ice_flow_add_fld_raw β€” sets the locations of a raw field from the entry's input buf, bestie πŸ’…

(this one lives in the Kernel API Manual, section 9, iykyk πŸŽ€)


✨ SYNOPSIS ✨

void ice_flow_add_fld_raw (struct ice_flow_seg_info *seg , u16 off , u8
len , u16 val_loc , u16 mask_loc );

πŸŽ€ ARGUMENTS πŸŽ€

  • seg β€” the packet segment that the field you're setting actually belongs to, no cap 🫢
  • off β€” where the raw field starts, measured in bytes from the beginning of the segment
  • len β€” the length of the raw pattern you wanna match
  • val_loc β€” the location of the value to match, taken from the entry's input buffer
  • mask_loc β€” the location of the mask value, also from the entry's input buffer

πŸ’– DESCRIPTION πŸ’–

okay so here's the vibe: this function specifies the offset of the raw field to be matched, counted from the beginning of the specified packet segment ✨ and it also specifies the locations β€” as byte offsets from the start of a flow entry's input buffer β€” of where the value to match and the mask value get extracted from.

Those locations then get stored in the flow profile. and like, when you're adding flow entries to the associated flow profile, those same locations can be used to quickly extract the values so you can build the content of a match entry. it's giving efficient. it's giving main character energy πŸ‘‘

⚠️ real talk though: this function should only be used for fixed-size data structures. fixed-size only, bestie, don't play yourself 😭

πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file itself, right here: ./drivers/net/ethernet/intel/ice/ice_flow.c πŸ“

and the whole extended friend group:


and that's the whole page, periodt πŸ«ΆπŸ’œ this little icon came from ./drivers/net/ethernet/intel/ice and it's dated October 2026 β€” go off, ice_flow_add_fld_raw(9), you ate πŸ’…βœ¨

πŸ“¦ where this page comes from