ovs_vport_free(9)

🎀 ovs_vport_free(9) 🎀

okay bestie, welcome to the kernel API manual, section 9, and today's main character is ovs_vport_free — yes that's the (9) up there, we're in kernel-land now 💅

---

✨ NAME ✨

ovs_vport_free — uninitialize and free vport

like, it uninitializes AND frees. a whole double-threat. 🔥

---

🌸 SYNOPSIS 🌸

void ovs_vport_free (struct vport *vport );

that's it. that's the whole vibe. void return, no notes, no cap. 🫶

---

🦋 ARGUMENTS 🦋

• vport — the vport to free ✨. the one getting un-alived (structurally speaking). the whole point of this function, honestly.

---

💖 DESCRIPTION 💖

so here's the tea 🍓: this frees a vport that was allocated with vport_alloc when it's no longer needed. like when you're done with something and you're like "okay this has served its purpose, thank you for your service, goodbye" — that's this. declutter era. it's giving cleanup arc. 🧹✨

⚠️ but bestie, listen to me — the caller must ensure that an RCU grace period has passed since the last time vport was in a datapath. this is not a suggestion, this is not a "probably fine", this is a hard requirement. if you skip the grace period, that's 💀 behaviour. don't do it. the vibes will not be immaculate, they will be undefined and crashy. 😭

so yes — free your vport, but do it responsibly. main character energy includes accountability. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./net/openvswitch/vport.c
• ovs_vport_init(9)
• ovs_vport_exit(9)
• ovs_vport_locate(9)
• ovs_vport_alloc(9)
• ovs_vport_add(9)
• ovs_vport_del(9)
• ovs_vport_get_stats(9)
• ovs_vport_get_upcall_stats(9)
• ovs_vport_set_upcall_portids(9)
• ovs_vport_get_upcall_portids(9)
• ovs_vport_find_upcall_portid(9)
• ovs_vport_receive(9)

that's the whole friend group right there — the ovs_vport_* gang. go say hi. iykyk 🌸🦋

---

and that's the page, bestie!! brought to you by ./net/openvswitch, dated October 2026, filed under kernel API manual, section 9 — ovs_vport_free(9) and out ✨💜🫶