qed_iov_get_next_active_vf(9)
π qed_iov_get_next_active_vf π
okay so bestie, welcome to the Kernel API Manual β¨ β this one's a little function from the qed driver family, and honestly? it's giving "tiny but crucial" energy. it does exactly one thing and it does it iconically π
β¨ NAME β¨
qed_iov_get_next_active_vf β give it a VF index, and it hands you back the index of the next active VF (including that one, okay? like it counts the one you passed in too π«Ά).
πΈ SYNOPSIS πΈ
u16 qed_iov_get_next_active_vf (struct qed_hwfn *p_hwfn , u16 rel_vf_id
);
literally just two args, no drama, no cap π
π¦ ARGUMENTS π¦
p_hwfnβ the HW device data. that's your hardware function context, the whole vibe source πrel_vf_idβ a VF ID. yep. that's the one π
π RETURN π
so if there are no further active VFs, you get MAX_NUM_VFS back π. otherwise? you get the index of the next active VF, slay β¨
π SEE ALSO π
get into it, bestie β these are all in the kernel file ./drivers/net/ethernet/qlogic/qed/qed_sriov.h π:
qed_iov_is_valid_vfid(9)qed_iov_hw_info(9)qed_add_tlv(9)qed_dp_tlv_list(9)qed_sriov_vfpf_malicious(9)qed_sriov_eqe_event(9)qed_iov_alloc(9)qed_iov_setup(9)qed_iov_free(9)qed_iov_free_hw_info(9)qed_iov_mark_vf_flr(9)qed_iov_search_list_tlvs(9)
lowkey a whole friend group fr fr π§
mwah π that's the whole page. go read your VFs responsibly.
and that's a wrap, babes π this came out of ./drivers/net/ethernet/qlogic/qed and it's dated October 2026 β iconic era, honestly πβ¨
π¦ 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