STRUCT IDPF_VECTOR_INFO(9)
π struct idpf_vector_info(9) π
okay so this is a page straight out of the Kernel API Manual (section 9, bestie, we're in the kernel docs now π₯) and it's about struct idpf_vector_info β a literal utility structure whose whole entire job is to pass function arguments as a structure. that's it. that's the gig. she's a little carrier pigeon for your args ποΈβ¨
π NAME π
struct idpf_vector_info β a utility structure to pass function arguments as a structure π
like, she doesn't do anything, she just holds things. main character energy, honestly π
β¨ SYNOPSIS β¨
struct idpf_vector_info {
u16 num_req_vecs;
u16 num_curr_vecs;
u16 index;
bool default_vport;
};
(no cap, that trailing }; with the space before it is exactly how it's written, we do not touch it π)
π¦ MEMBERS π¦
num_req_vecsβ the vectors you actually need, based on how many queues the user updated viaethtool. this is the wishlist πnum_curr_vecsβ the current number of vectors. and heads up bestie, this one must be >=num_req_vecsβ οΈ β that's not a suggestion, that's the rule, periodt.indexβ the relative starting index for vectors. like where you're hopping on the bus πdefault_vportβ yep, abool, and if it's set, the vectors are for the default vport. simple as π
π SEE ALSO π
this is the part where the whole friend group shows up, and i mean the whole friend group β they all live in the kernel file ./drivers/net/ethernet/intel/idpf/idpf.h:
struct idpf_mac_filter(9)enum idpf_state(9)enum idpf_flags(9)enum idpf_cap_field(9)enum idpf_vport_state(9)struct idpf_netdev_priv(9)struct idpf_reset_reg(9)struct idpf_vport_max_q(9)struct idpf_reg_ops(9)struct idpf_dev_ops(9)enum idpf_vport_reset_cause(9)enum idpf_vport_flags(9)struct idpf_tstamp_stats(9)struct idpf_q_vec_rsrc(9)struct idpf_vport(9)enum idpf_user_flags(9)struct idpf_rss_data(9)struct idpf_q_coalesce(9)struct idpf_vport_user_config_data(9)enum idpf_vport_config_flags(9)struct idpf_avail_queue_info(9)struct idpf_vector_lifo(9)struct idpf_queue_id_reg_chunk(9)struct idpf_queue_id_reg_info(9)struct idpf_vport_config(9)struct idpf_adapter(9)idpf_is_queue_model_split(9)idpf_is_rdma_cap_ena(9)idpf_get_reserved_vecs(9)idpf_get_reserved_rdma_vecs(9)idpf_get_default_vports(9)idpf_get_max_vports(9)idpf_get_max_tx_bufs(9)idpf_get_min_tx_pkt_len(9)idpf_is_reset_detected(9)idpf_is_reset_in_prog(9)idpf_netdev_to_vport(9)idpf_netdev_to_adapter(9)idpf_is_feature_ena(9)idpf_get_max_tx_hdr_size(9)idpf_vport_ctrl_lock(9)idpf_vport_ctrl_unlock(9)
like i said. everyone. bring snacks π«Άππ
fr fr though βnum_curr_vecs>=num_req_vecsis the one thing to remember. don't be the person who forgets π
and that's the page!! credit where it's due: this one comes from ./drivers/net/ethernet/intel/idpf, dated October 2026, and it's filed under the Kernel API Manual, section struct idpf_vector_info(9). slay, documented, iconic, periodt πβ¨π
π¦ 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