STRUCT MV88E6XXX_DEVLINK_VTU_ENTRY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay bestie, welcome to the Kernel API Manual page for struct mv88e...nk_vtu_entry(9) β€” the NAME line says struct mv88e6xxx_devlink_vtu_entry and it's the Devlink VTU entry. That's the title tea, periodt. πŸ’…

✨ SYNOPSIS ✨

       struct mv88e6xxx_devlink_vtu_entry {
           u16 fid;
           u16 sid;
           u16 op;
           u16 vid;
           u16 data[3];
           u16 resvd;
        };

🫢 Members 🫢

  • fid β€” Global1/2: FID and VLAN policy.
  • sid β€” Global1/3: SID, unknown filters and learning.
  • op β€” Global1/5: FID (old chipsets).
  • vid β€” Global1/6: VID, valid, and page.
  • data β€” Global1/7-9: Membership data and priority override.
  • resvd β€” Reserved. Also happens to align the size to 16B.

πŸ’… Description πŸ’…

okay so the VTU entry format varies between chipset generations β€” the descriptions above represent the superset of all possible information, and not all fields are valid on all devices. Since this is a low-level debug interface, copy all data verbatim and defer parsing to the consumer. That's the whole assignment, bestie. 🫢

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/net/dsa/mv88e6xxx/devlink.c
  • struct mv88e6xxx_devlink_stu_entry(9)

xoxo πŸ’– signing off from ./drivers/net/dsa/mv88e6xxx, dated October 2026, still repping struct mv88e...nk_vtu_entry(9) β€” slay your debugging, bestie βœ¨πŸ’…

πŸ“¦ where this page comes from