mlx4_ALLOCATE_VPP_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 🌈


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