ice_vf_verify_rx_desc(9)
π ice_vf_verify_rx_desc β verify received FDIR programming status descriptor β¨
okay so bestie, welcome to the Kernel API Manual π«Ά β this one lives in the ice_vf_verify_rx_desc(9) corner of the universe and it's literally the vibe check for an FDIR programming status descriptor that just showed up in your RX queue πΈ
π NAME π
ice_vf_verify_rx_desc β no cap, its whole job is to verify received FDIR programming status descriptor. that's it. that's the function. iconic behaviour honestly π
β SYNOPSIS β
int ice_vf_verify_rx_desc (struct ice_vf *vf , struct ice_vf_fdir_ctx
*ctx , enum virtchnl_fdir_prgm_status *status );
three args, one int back. she's giving "small function, big responsibilities" energy π
π¦ ARGUMENTS π¦
vfβ pointer to the VF info π this is the VF's whole little info situation, handed over as a pointer.ctxβ FDIR context info for post processing π§ like, the context you're gonna need after the fact. post-processing tea.statusβ virtchnl FDIR program status π the virtchnl-flavoured status of the FDIR program. it's right there in the name bestie.
π₯ RETURN π₯
0on success β¨- and other on error π (yes, "other". that's the actual wording. we don't know which others. it's a mystery. it's giving suspense.)
π SEE ALSO π
first up, the kernel file it actually lives in:
- Kernel file
./drivers/net/ethernet/intel/ice/virt/fdir.cπ
and then the whole extended friend group β literally the entire FDIR cinematic universe, all present and accounted for:
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_write_flow_prof(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_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, forty-two functions. forty-two!! she said "you WILL meet my whole family" ππ
ngl bestie, if you're here you're probably deep in the Intel ice driver's VF FDIR code. hydrate. take breaks. the FDIR rabbit hole is real π«Ά
and that's the whole page!! π source-wise this came from ./drivers/net/ethernet/intel/i... (yes it's literally truncated in the original, we respect the ellipsis π), dated October 2026, sitting under the ice_vf_verify_rx_desc(9) title in the Kernel API Manual. mwah, bye bestie π
πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms