ice_vc_fdir_write_flow_prof(9)

💖 NAME 💖

okay so welcome to the ice_vc_fdir_write_flow_prof(9) page, bestie — that's the function name right there, and the manual it lives in is the Kernel API Manual, so you know it's the real deal ✨

and like... the NAME line in the original is literally just the function name followed by a lone - and nothing else 💀 no summary, no lil tagline, nothing. she said "my name is enough." and honestly? iconic. main character energy fr.

---

🌸 SYNOPSIS 🌸

here's the whole signature, copied exactly so nobody comes for me:

int ice_vc_fdir_write_flow_prof (struct ice_vf *vf , enum ice_fltr_ptype
flow , struct ice_flow_seg_info *seg , int tun );

yes the commas have spaces before them. no i will not be fixing that. we respect the source 💅

---

🎀 ARGUMENTS 🎀

• vf — pointer to the VF structure. that's the virtual function she's working on 🫶
• flow — the filter flow type, an enum ice_fltr_ptype. it's giving "what kind of traffic are we even talking about" 🌈
• seg — an array of one or more packet segments that describe the flow. literally the shape of your packet, segment by segment 🧚
• tun — the tunnel vibe check: 0 implies a non-tunnel type filter, 1 implies a tunnel type filter. binary queen 👑

---

🦋 DESCRIPTION 🦋

so what does she actually do? she writes the flow's profile config and the packet segment into the hardware. that's it. that's the whole thing. hardware gets the profile, hardware gets the segments, done 🔥

---

⭐ RETURN ⭐

• 0 on success 🎉
• and other on error 😭 (yes, "other" — that's what the page says and i'm not about to invent numbers that aren't there, ngl)

no cap: if you get back something that isn't 0, something went sideways. the page does not elaborate further, so i won't either 🙈

---

👑 SEE ALSO 👑

first up, the kernel file, exactly as written:

Kernel file ./drivers/net/ethernet/intel/ice/virt/fdir.c

and now the whole friend group — every single one of these, in order, no skips 💜

ice_vc_fdir_param_check(9), ice_vf_start_ctrl_vsi(9), ice_vc_fdir_alloc_prof(9), ice_vc_fdir_free_prof(9), ice_vc_fdir_free_prof_all(9), ice_vc_fdir_parse_flow_fld(9), ice_vc_fdir_set_flow_fld(9), ice_vc_fdir_set_flow_hdr(9), ice_vc_fdir_rem_prof(9), ice_vc_fdir_rem_prof_all(9), ice_vc_fdir_reset_cnt_all(9), ice_vc_fdir_has_prof_conflict(9), ice_vc_fdir_config_input_set(9), ice_vc_fdir_is_raw_flow(9), ice_vc_fdir_parse_raw(9), ice_vc_fdir_parse_pattern(9), ice_vc_fdir_parse_action(9), ice_vc_validate_fdir_fltr(9), ice_vc_fdir_comp_rules(9), ice_vc_fdir_is_dup_fltr(9), ice_vc_fdir_insert_entry(9), ice_vc_fdir_remove_entry(9), ice_vc_fdir_lookup_entry(9), ice_vc_fdir_flush_entry(9), ice_vc_fdir_write_fltr(9), ice_vf_fdir_timer(9), ice_vc_fdir_irq_handler(9), ice_vf_fdir_dump_info(9), ice_vf_verify_rx_desc(9), ice_vc_add_fdir_fltr_post(9), ice_vc_del_fdir_fltr_post(9), ice_flush_fdir_ctx(9), ice_vc_fdir_set_irq_ctx(9), ice_vc_fdir_clear_irq_ctx(9), ice_vc_parser_fv_check_diff(9), ice_vc_parser_fv_save(9), ice_vc_add_fdir_raw(9), ice_vc_add_fdir_fltr(9), ice_vc_del_fdir_raw(9), ice_vc_del_fdir_fltr(9), ice_vf_fdir_init(9), ice_vf_fdir_exit(9)

like, that's the entire fdir cinematic universe and she's related to all of them 🍓

---

and that's the page!! mwah 💋 before you go — the source for all this lives at ./drivers/net/ethernet/intel/i... (the original really does cut off right there, no i'm not hiding the rest from you 😭) and this edition is dated October 2026, so jot that down in your notes app. stan fdir.c, stay hydrated, and don't forget your tun flag bestie 🫶💖✨