mlx5dv_devx_query_eqn(3)

Hey bestie 💖 welcome to the mlx5dv_devx_query_eqn(3) manual page — that's the manual name, and we're about to query an EQN for a vector id together. No cap, it's lowkey niche but highkey useful. ✨

🌸 NAME 🌸

mlx5dv_devx_query_eqn — Query EQN for a given vector id. 💅

🦋 SYNOPSIS 🦋

#include <infiniband/mlx5dv.h>

int mlx5dv_devx_query_eqn(struct ibv_context *context, uint32_t vector,
                          uint32_t *eqn);

💅 DESCRIPTION 💅

Okay so this one queries the EQN for a given input vector, and the EQN is needed for other device commands over the DEVX interface. It's giving essential background information, bestie. 🫶

The DEVX API enables direct access from the user space area to the mlx5 device driver, and the EQN information is needed for few commands such as CQ creation. Literally iconic for that whole situation. 👑

🎀 ARGUMENTS 🎀

• context — RDMA device context to work on. That's the device context, obviously. 💖
• vector — Completion vector number. Just the number, no cap. 🔥
• eqn — The device EQ number which relates to the given input vector. It's giving “EQN for your vector” energy. ✨

🌈 RETURN VALUE 🌈

Returns 0 on success, or the value of errno on failure (which indicates the failure reason). So if it's not 0, errno is the one telling you why it failed — that's the tea. ☕

🧚 SEE ALSO 🧚

Go give these besties a look: mlx5dv_open_device, mlx5dv_devx_obj_create. 💜

👑 AUTHOR 👑

The source has a #AUTHOR marker here, and the icon behind this page is Yishai Hadas <yishaih@mellanox.com>. 🫶

---

Footer check, bestie: the page footer is just mlx5dv_devx_query_eqn(3) again — no extra source/version or date text is shown, so that's the entire cute sign-off. Stay slay, query those EQNs, and hydrate. 💅💖