ovs_vport_add(9)

💅 ovs_vport_add(9) — the Kernel API Manual, but make it make sense 🫶

okay so bestie, we're in the Kernel API Manual today, section 9, and the star of the show is ovs_vport_add(9). yes it's giving kernel-internals, yes it's iconic, no you don't need to be scared. let's go 💖

---

✨ NAME ✨

ovs_vport_add — adds a vport device (this one's for the kernel callers out there, iykyk 👑)

🌸 SYNOPSIS 🌸

struct vport * ovs_vport_add (const struct vport_parms *parms );

like literally that's the whole thing. returns a struct vport *, takes a const struct vport_parms * called parms. slay. ✨

🦋 ARGUMENTS 🦋

• parms — all the info about the new vport we're about to birth into existence. the details, the lore, the whole vibe check for the fresh vport. 🎀

💜 DESCRIPTION 💜

so what does it actually do? it creates a brand-new vport with the configuration you specified — and heads up, what that configuration even means is dependent on the device type, so no two device types are gonna read it the same way, k? 👀

⚠️ non-negotiable, fr fr: ovs_mutex must be held. not "should", not "maybe", must. don't be the main character who forgets the mutex. 💀

⭐ SEE ALSO ⭐

go look at the kernel file ./net/openvswitch/vport.c (that's the source of truth, bestie) and also these absolutely iconic siblings:

• ovs_vport_init(9)
• ovs_vport_exit(9)
• ovs_vport_locate(9)
• ovs_vport_alloc(9)
• ovs_vport_free(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)

the whole friend group, together again 😭🫶

---

and that's the tea 🍓 — courtesy of ./net/openvswitch, dated October 2026. go hold that mutex and stan vports responsibly. mwah 💋🌈