IBV_QUERY_PKEY(3)

📦
version 62.0 · 9 versions
, in alpine 3.24, centos-stream 10, centos-stream 9, ubuntu jammy

💅 ibv_query_pkey — like, the InfiniBand port P_Key table lookup bestie

okay so this is a page from the Libibverbs Programmer's Manual, and it's literally about peeking at one single entry in an InfiniBand port's P_Key table. tiny function, big main character energy. 🎀

✨ NAME ✨

ibv_query_pkey — query an InfiniBand port's P_Key table 🦋

like… you want one P_Key? this is the girl who gets you that P_Key.

🌸 SYNOPSIS 🌸

#include <infiniband/verbs.h>

int ibv_query_pkey(struct ibv_context *context,
                   uint8_t port_num,
                   int index,
                   uint16_t *pkey);

no cap, that's the whole vibe. four args, one int coming back at you. ✨

💖 DESCRIPTION 💖

ibv_query_pkey() hands you back the P_Key value for the device context context, on port port_num, at the entry called index — and it writes it out through the pointer pkey. 🫶

and bestie, important detail: the P_Key value comes back in network byte order. not host byte order. network. byte. order. write that on your mirror fr fr 💅

so like, context = which device, port_num = which port, index = which entry in that port's P_Key table, pkey = where the answer lands. one entry, one answer, iconic behaviour only. 👑

⭐ RETURN VALUE ⭐

  • 0 — slay, it worked ✨ success bestie
  • -1 — nope, error 😭 that's the whole deal

🦋 SEE ALSO 🦋

the friend group, all of them holding hands:

🌈 AUTHOR 🌈

Dotan Barak <dotanba@gmail.com> — respectfully, legend behaviour 💜

🧚 little reminder before you go: index picks the entry, pkey takes the value, and that value is in network byte order. do not come for me later if you forget. 🙈

and that's the whole page, gorgeous. brought to you by libibverbs, dated 2006-10-31 — yeah she's vintage but she still ate 💅🎀

📦 where this page comes from