mlx4_ALLOCATE_VPP_get(9)
π mlx4_ALLOCATE_VPP_get(9) π
okay so bestie, we're in the Kernel API Manual today and this page is literally all about mlx4_ALLOCATE_VPP_get β the little function that queries your port's VPP resources and how they're allocated. iykyk π
β¨ NAME β¨
mlx4_ALLOCATE_VPP_get β query port VPP available resources and allocation. ngl, the timing here matters: before distribution of VPPs to priorities, only available_vpp is returned. After initialization? It returns the distribution of VPPs among priorities. π¦
πΈ SYNOPSIS πΈ
int mlx4_ALLOCATE_VPP_get (struct mlx4_dev *dev , u8 port , u16
*available_vpp , u8 *vpp_p_up );
π ARGUMENTS π
devβ mlx4_dev. that's the device, she's the main character πportβ physical port number. fr fr, the actual physical one.available_vppβ pointer to the variable where the number of available VPPs gets stored. so like, the count lives here πvpp_p_upβ the distribution of VPPs to priorities is stored in this array. π
π§ DESCRIPTION π§
Returns 0 on success or a negative mlx4_core errno code. that's it, that's the vibe check. π
bestie please actually check that return value, negative errno codes are not it π
π SEE ALSO π
- Kernel file
./drivers/net/ethernet/mellanox/mlx4/fw_qos.hβ the source of truth, go read it π«Ά mlx4_SET_PORT_PRIO2TC(9)mlx4_SET_PORT_SCHEDULER(9)mlx4_ALLOCATE_VPP_set(9)mlx4_SET_VPORT_QOS_get(9)mlx4_SET_VPORT_QOS_set(9)
okay that's the whole page, you ate that π
β¨ this icon was brought to you by ./drivers/net/ethernet/mellano..., version October 2026 β slay, see you in the group chat π¦ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms