ice_vc_fdir_...ig_input_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ice_vc_fdir_config_input_set β€” bestie, this is the one that sets up your input set for you, no cap ✨

(oh and hey β€” welcome to the ice_vc_fdir_...ig_input_set(9) page, Kernel API Manual energy, let's go 🫢)


✨ SYNOPSIS ✨

int ice_vc_fdir_config_input_set (struct ice_vf *vf , struct
virtchnl_fdir_add *fltr , struct virtchnl_fdir_fltr_conf *conf , int tun
);

πŸŽ€ ARGUMENTS πŸŽ€

  • vf β€” pointer to the VF structure πŸ’– literally just a pointer, she's pointing at the VF struct, that's her whole job
  • fltr β€” the virtual channel add cmd buffer, iconic little container, we love her
  • conf β€” the FDIR configuration for each filter 🌸 one config per filter, as she deserves
  • tun β€” okay so 0 implies non-tunnel type filter, and 1 implies tunnel type filter πŸ¦‹ that's it, those are the two vibes

🌈 DESCRIPTION 🌈

Config the input set type and value for virtual channel add msg buffer 😭✨ yes bestie she literally configures the input set type and value for the virtual channel add msg buffer. That's the whole main character moment. Nothing more, nothing less. Periodt πŸ’…


πŸ”₯ RETURN πŸ”₯

0 on success, and other on error πŸ’€ (yes, "other" β€” she's mysterious like that, highkey not giving us specifics)


πŸ‘‘ SEE ALSO πŸ‘‘

Okay bestie, buckle up, this is the whole group chat β€” every single one of these is invited to the function πŸŽ‰

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

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_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)

πŸ’€ friendly reminder bestie: this page is a kernel API page, so if you're out here calling it from userspace you're gonna have a bad time β€” it's (9) energy, section nine, kernel devs only, iykyk 🧚

okay that's the page!! mwah πŸ’‹ this came from ./drivers/net/ethernet/intel/i... and it's dated October 2026, and the header/footer both rep ice_vc_fdir_...ig_input_set(9) β€” slay, go forth and configure those input sets πŸŒΈπŸ¦‹πŸ’–

πŸ“¦ where this page comes from