mlx5_esw_query_functions(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mlx5_esw_query_functions — okay bestie, let's talk ✨

So this is a page from the Kernel API Manual, and the function we're stanning today is literally called mlx5_esw_query_functions. Yes that's a mouthful, yes it's iconic, no we're not shortening it. 🎀

🌸 NAME 🌸

mlx5_esw_query_functions — returns raw output about functions state. That's the whole vibe. It gives you the raw deets on what's up with the functions, no filter, no cleanup, just vibes and bytes. 💖

✨ SYNOPSIS ✨

const u32 * mlx5_esw_query_functions (struct mlx5_core_dev *dev );

Periodt. That's the signature. Look at that const u32 * — it's giving pointer-to-const, main character energy. 👑

🦋 ARGUMENTS 🦋

  • dev — pointer to the device you wanna query, bestie. That's it. That's the whole argument list. Just hand over the device and let it cook. 🔥

💜 DESCRIPTION 💜

Okay so here's the tea, fr fr:

mlx5_esw_query_functions allocates and returns a functions changed raw output memory pointer from the device on success. Slay. It went and got you the goods. 🫶

Otherwise? It returns ERR_PTR. 💀 Yeah. Not a real pointer, an error wearing a pointer's outfit. Check before you dereference, iykyk.

⚠️ The rule that is NOT optional: the caller must free the memory using kvfree when a valid pointer is returned. Not kfree. Not vibes. kvfree. If you skip this you're leaking memory and that's not the aesthetic we're going for. 😭

🌈 SEE ALSO 🌈

Like, go read the source, it's literally right there:

  • Kernel file ./drivers/net/ethernet/mellanox/mlx5/core/eswitch.c

And the whole friend group, all of them, no cap:

✨ That's the whole page, bestie! ✨ Big love to the kernel source at ./drivers/net/ethernet/mellano... (yes the truncation is part of the lore 🎀) and to the October 2026 release date. Go free your kvfree-able memory and hydrate. 💅💖🌸

📦 where this page comes from