mlx4_SET_VPORT_QOS_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ mlx4_SET_VPORT_QOS_set(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this one's short but she's important β€” it's giving "small function, big responsibilities" energy, fr fr.


🌸 NAME 🌸

mlx4_SET_VPORT_QOS_set β€” sets the QoS properties of a Vport, periodt. πŸŽ€

So here's the tea: the QoS parameters can be modified at any time, which is lowkey iconic and flexible of them. BUT β€” and this is the important part, don't skip it β€” they must be initialized before any QP is associated with the VPort. Like, before. No exceptions. Timing is everything bestie, iykyk 😭


πŸ¦‹ SYNOPSIS πŸ¦‹

int mlx4_SET_VPORT_QOS_set (struct mlx4_dev *dev , u8 port , u8 vport ,
       struct mlx4_vport_qos_param *in_param );

Four args, one return value, zero drama. Slay. ✨


πŸ’– ARGUMENTS πŸ’–

  • dev β€” the mlx4_dev. your device of the moment, the main character πŸ‘‘
  • port β€” the physical port number. yes, physical. like, the actual hardware one 🌈
  • vport β€” the Vport id. which virtual port are we setting up, bestie? 🧚
  • in_param β€” an array of mlx4_vport_qos_param which holds the requested values. that's right, an array β€” it's carrying all your QoS wishes in one little bundle 🫢

πŸ”₯ DESCRIPTION πŸ”₯

Returns 0 on success, or a negative mlx4_core errno code. no cap, that's the whole description β€” she's brief but she's giving substance πŸ’€

real talk though: check that return value. a negative errno is the function telling you something went sideways πŸ™ˆ

⭐ SEE ALSO ⭐


and that's the whole page, babe πŸ’œ stay hydrated, read your errno codes, and remember to init your QoS params before the QP shows up, ok bye!! πŸŒΈπŸ¦‹βœ¨

./drivers/net/ethernet/mellano... β€” October 2026 β€” mlx4_SET_VPORT_QOS_set(9)

πŸ“¦ where this page comes from