mlx5dv_map_ah_to_qp(3)
π mlx5dv_map_ah_to_qp(3) π
okay so bestie, welcome to section 3 of the manual β mlx5dv_map_ah_to_qp, the little function that makes your address handle and your QP get along. genuinely iconic behavior, no cap.
β¨ NAME β¨
mlx5dv_map_ah_to_qp β maps the destination path information that lives in an address handle (AH) over to the info we pull out of the qp. it's giving matchmaker energy fr fr π
πΈ SYNOPSIS πΈ
#include <infiniband/mlx5dv.h>
int mlx5dv_map_ah_to_qp(struct ibv_ah *ah, uint32_t qp_num);
look at her. two arguments. immaculate. π«Ά
π¦ DESCRIPTION π¦
so what does this API actually do? it maps the destination path information sitting in the address handle (ah) to the information that gets extracted from the qp β think congestion control coming from ECE, iykyk. π«
this API is literally an enhancement to DC and UD QPs, and the whole point is better performance: it lets you use per-address congestion control (CC) algorithms, which means DC/UD QPs can run multiple CC algorithms inside the same datacenter. main character energy for your fabric, honestly. π₯
the mapping this API creates is implicitly destroyed when the address handle is destroyed, bestie. that's just how it goes.
and listen β it is not affected by the destruction of QP qp_num. so go ahead and yeet that QP, the mapping stays put. π
a duplicate mapping to the same address handle? ignored. because in that case this API is just a hint for the hardware, so it would do nothing and return success regardless of the new qp_num ECE. yes, regardless β that part matters. π
one more thing, and this is the part people miss: the function must be called after ECE negotiation/preconfiguration was done by some external means. don't skip that step, queen. π
π ARGUMENTS π
ahβ the target's address handle. the destination-vibe holder. πqp_numβ the initiator QP whose congestion control info gets extracted from its ECE. this is where the CC tea comes from. π
β RETURN VALUE β
- upon success β returns
0β¨ slay - upon failure β the value of
errnois returned π
π SEE ALSO π
go read those too, they're all part of the same friend group, fr fr. π§
π AUTHOR π
- Yochai Cohen <yochai@nvidia.com>
- Patrisious Haddad <phaddad@nvidia.com>
two legends. we stan. π
and that's the whole page!! the header up top says mlx5dv_map_ah_to_qp(3) and the footer at the bottom just repeats mlx5dv_map_ah_to_qp(3) with no fancy source/version or date info attached β so like, no extra lore there, sorry bestie π mwah, go map some AHs to some QPs, periodt. π
π¦ where this page comes from
- alpine 3.24: rdma-core-doc 61.0-r0 Β· GPL-2.0-only OR BSD-2-Clause
- centos-stream 10: rdma-core-devel 62.0-3.el10 Β· GPLv2 or BSD
- centos-stream 9: rdma-core-devel 61.0-3.el9 Β· GPLv2 or BSD
- centos-stream 9: rdma-core-devel 61.0-3.el9 Β· GPLv2 or BSD
- ubuntu jammy: libibverbs-dev 39.0-1 Β· BSD-MIT OR GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms