qed_iov_setup(9)
π qed_iov_setup(9) β okay bestie, let's talk SR-IOV setup
So you opened the Kernel API Manual (yes, the kernel API manual, we're fancy today π) and landed on qed_iov_setup. Iconic. Let's get into it, no cap.
β¨ NAME β¨
qed_iov_setup β the function that sets up sriov related resources. That's the whole vibe: it does the setup, it handles the sriov stuff, and it's literally the resource-wrangler of this little corner of the kernel π
πΈ SYNOPSIS πΈ
void qed_iov_setup (struct qed_hwfn *p_hwfn );
Yup, that's it. Returns nothing (void), takes one pointer. Short and slay β¨
π¦ ARGUMENTS π¦
p_hwfnβ HW device data. That's the hardware device info your function needs to do its thing π«Ά
β RETURN β
Void. It gives you nothing back. Not a value, not an error code, not a lil wave goodbye. Void. Periodt π
Ngl, that means whatever happens in there, you're not getting a return value telling you about it. That's just how it is β don't come for me, I'm only the messenger π
π SEE ALSO π
So there's a whole squad of related stuff you should lowkey check out. First up, the Kernel file:
./drivers/net/ethernet/qlogic/qed/qed_sriov.h
And then the friend group π:
qed_iov_is_valid_vfid(9)qed_iov_get_next_active_vf(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_free(9)qed_iov_free_hw_info(9)qed_iov_mark_vf_flr(9)qed_iov_search_list_tlvs(9)
That's the roster. Go read them, they're all main character energy in their own way π
Okay that's the whole page, bestie β nothing hidden, nothing skipped, we ate and left no crumbs π
πΈ Cute little sign-off: this gem lives in ./drivers/net/ethernet/qlogic/qed, and it's dated October 2026. Mark your calendars, iykyk πβ¨
π¦ 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