mlx4_SET_VPORT_QOS_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mlx4_SET_VPORT_QOS_get β€” kernel API manual, but make it cute

okay so bestie, you're looking at the manual page for mlx4_SET_VPORT_QOS_get (that's the kernel API manual, section 9, iykyk). It's a getter. It's giving "let me peek at the settings, not change them." Let's go πŸŽ€


✨ NAME ✨

mlx4_SET_VPORT_QOS_get β€” query the QoS properties of a Vport. So basically every priority that's allowed for the Vport gets assigned a share of the BW, plus a BW limitation β€” and this command queries the current QoS values. It's the "look, don't touch" of the QoS world 🫢


🌸 SYNOPSIS 🌸

int mlx4_SET_VPORT_QOS_get (struct mlx4_dev *dev , u8 port , u8 vport ,
struct mlx4_vport_qos_param *out_param );

That's the whole vibe. Four args, one int coming back at you πŸ’«


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” your mlx4_dev. The main character, fr.
  • port β€” the physical port number. Which port, bestie? This one.
  • vport β€” the Vport id. Gotta know which vport we're snooping on.
  • out_param β€” an array of mlx4_vport_qos_param that will contain the values. It's the container, it's the vessel, it's where the answers land πŸ’–

πŸ’œ DESCRIPTION πŸ’œ

Returns 0 on success, or a negative mlx4_core errno code. That's it. That's the whole description. Zero is the slay outcome, negative is the "oop 😭" outcome.

ngl, that's all the page gives us on behaviour, so no extra lore from me β€” I'm not out here inventing facts, that's not the move πŸ™ˆ

🌈 SEE ALSO 🌈


🧚 the cute lil sign-off 🧚

This icon of a page comes to you from ./drivers/net/ethernet/mellano... and it's dated October 2026, under the manual name mlx4_SET_VPORT_QOS_get(9). Yes the path is literally truncated in the original, no I'm not fixing it, I don't make the rules πŸ’…βœ¨

Now go query those QoS values, you absolute icon πŸ‘‘πŸ“

πŸ“¦ where this page comes from