i40e_notify...of_vf_enable(9)

💖 i40e_notify...of_vf_enable(9) 💖

okay bestie, welcome to the Kernel API Manual ✨ — yes that's the manual name, and yes this page is literally called i40e_notify...of_vf_enable(9) and no, the ellipsis isn't me being dramatic, that's just how the kernel names things 😭

---

🌸 NAME 🌸

i40e_notify_client_of_vf_enable — the way it just… calls the client's VF notification callback 🎀

---

🦋 SYNOPSIS 🦋

void i40e_notify_client_of_vf_enable (struct i40e_pf *pf , u32 num_vfs );

like, that's the whole vibe. one function, two args, no cap 💅

---

⭐ ARGUMENTS ⭐

• pf — the PF device pointer 🫶 (your main character struct, fr)
• num_vfs — the number of VFs currently enabled, and 0 means disable 👑 lowkey important detail, don't sleep on it

---

✨ DESCRIPTION ✨

so here's the tea 🍓 — if there's a client attached to this PF, it calls that client's VF notification routine. that's it. that's the whole function. iconic behaviour, honestly 🌈

ngl, "if there is a client attached" is doing a LOT of work in that sentence — no client, no call. just so we're clear 💜

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/net/ethernet/intel/i40e/i40e_client.c — go read it, iykyk 📖

and the whole friend group 💖:

• i40e_client_get_params(9)
• i40e_notify_client_of_vf_msg(9)
• i40e_notify_client_of_l2_param_changes(9)
• i40e_client_release_qvlist(9)
• i40e_notify_client_of_netdev_close(9)
• i40e_notify_client_of_vf_reset(9)
• i40e_vf_client_capable(9)
• i40e_client_add_instance(9)
• i40e_client_del_instance(9)
• i40e_client_subtask(9)
• i40e_lan_add_device(9)
• i40e_lan_del_device(9)
• i40e_client_virtchnl_send(9)
• i40e_client_setup_qvlist(9)
• i40e_client_request_reset(9)
• i40e_client_update_vsi_ctxt(9)

---

and that's the page, bestie 🧚💜 — brought to you by the source tree at ./drivers/net/ethernet/intel/i40e, dated October 2026, and titled i40e_notify...of_vf_enable(9) because the kernel loves a mysterious ellipsis. slay 💅✨