mlx4_ALLOCATE_VPP_set(9)

💖 mlx4_ALLOCATE_VPP_set(9) — Kernel API Manual 💖

okay so bestie, this is the Kernel API Manual page for mlx4_ALLOCATE_VPP_set(9), and it's lowkey all about handing out VPPs to different priorities. The rules are strict, no cap. 🎀

✨ NAME ✨

mlx4_ALLOCATE_VPP_set — Distribution of VPPs among different priorities. The total number of VPPs assigned to all for a port must not exceed the value reported by available_vpp in mlx4_ALLOCATE_VPP_get. VPP allocation is allowed only after the port type has been set, and while no QPs are open for this port.

🚨 bestie, read this twice: the total number of VPPs assigned to all for a port must not exceed the value reported by available_vpp in mlx4_ALLOCATE_VPP_get. VPP allocation is allowed only after the port type has been set, and while no QPs are open for this port. That's the vibe check, fr fr.

🛠️ SYNOPSIS 🛠️

int mlx4_ALLOCATE_VPP_set (struct mlx4_dev *dev , u8 port , u8 *vpp_p_up
);

🎀 ARGUMENTS 🎀

• dev — mlx4_dev. That's the device, bestie.
• port — Physical port number.
• vpp_p_up — Allocation of VPPs to different priorities.

💫 DESCRIPTION 💫

Returns 0 on success or a negative mlx4_core errno code. That's the whole return-value moment: 0 is the slay, a negative mlx4_core errno code is the nope. 💅

🔗 SEE ALSO 🔗

• Kernel file ./drivers/net/ethernet/mellanox/mlx4/fw_qos.h
• mlx4_SET_PORT_PRIO2TC(9)
• mlx4_SET_PORT_SCHEDULER(9)
• mlx4_ALLOCATE_VPP_get(9)
• mlx4_SET_VPORT_QOS_get(9)
• mlx4_SET_VPORT_QOS_set(9)

Okay bestie, that's the whole page 💅 — cute sign-off from source/version ./drivers/net/ethernet/mellano..., dated October 2026, as mlx4_ALLOCATE_VPP_set(9) 🫶✨