MLX5DV(7)

πŸ’– MLX5DV πŸ’–

ok so bestie, welcome to the mlx5dv manual page β€” that's mlx5dv, direct verbs for mlx5 devices, living in the Miscellaneous Information Manual like the icon it is. ✨

Basically: this is low level access to mlx5 devices so you can do your data path operations and literally skip the general branching that ibv_post_send(3) makes you sit through. no cap. πŸ’…


🌸 NAME 🌸

mlx5dv β€” Direct verbs for mlx5 devices.

This is low level access to mlx5 devices to perform data path operations, without general branching performed by ibv_post_send(3).


✨ DESCRIPTION ✨

Okay so here's the tea, bestie. πŸ“

The libibverbs API is an abstract one. It's agnostic to any underlying provider specific implementation β€” it doesn't care who's underneath, it just vibes. And like, that abstraction has a genuine advantage: user applications portability. Your app can hop between providers and nobody's mad. πŸ¦‹

But β€” and this is the part nobody warns you about β€” it has a performance penalty. The abstraction tax is real. 😭

For some applications, optimizing performance is more important than portability. That's just the truth.

The mlx5 direct verbs API is intended for such applications. It exposes mlx5 specific low level data path (send / receive / completion) operations, letting the application bypass the libibverbs data path API entirely. main character energy tbh. πŸ‘‘

This interface consists from one hardware specific header file with relevant inline functions and conversion logic from ibverbs structures to mlx5 specific structures.

The direct include of mlx5dv.h together with linkage to mlx5 library will allow usage of this new interface.

🚨 bestie listen β€” once an application uses the direct flow, the locking scheme is fully managed by itself. There is an expectation that no mixed flows in the data path for both direct/non-direct access will be by same application. so don't mix, fr fr. πŸ™ˆ

πŸ“ NOTES πŸ“

All Mellanox NIC devices starting from Connect-IB (Connect-IB, ConnectX-4, ConnectX-4Lx, ConnectX-5, ...) implement the mlx5 API. ✨

So using the mlx5 direct verbs does not limit the applications to a single NIC HW device β€” which means you keep some level of portability. not me being shocked that you can have both. πŸ’€πŸ’–


πŸ‘€ SEE ALSO πŸ‘€


🫢 AUTHORS 🫢

Leon Romanovsky <leonro@mellanox.com> β€” thank you for your service, king. 🌈⭐


and that's the whole page bestie!! πŸ’œ this was version 1.0.0, dated 2017-02-02, and it's the MLX5DV(7) page from the Miscellaneous Information Manual. slay, go forth and bypass that data path API. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from