qed_iov_get_next_active_vf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 πŸ“:

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