rdma_query_gid_table(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ rdma_query_gid_table(9) ✨

okay so bestie, we're in the kernel API manual today β€” this one's from the rdma_query_gid_table(9) part of the book, and it's actually such a serve, let me tell you 🫢


πŸ’œ NAME πŸ’œ

rdma_query_gid_table β€” reads GID table entries of all the ports of a device, up to max_entries. that's it, that's the vibe πŸ’…


🌸 SYNOPSIS 🌸

ssize_t rdma_query_gid_table (struct ib_device *device , struct ib_uverbs_gid_entry *entries , size_t max_entries );

like, yes, that whole line is the function. she's long, she's iconic, she ate πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • device β€” the device we're querying, bestie. that's the one we're pulling info out of πŸ’–
  • entries β€” the entries where the GID entries get returned. that's where the ✨results✨ land.
  • max_entries β€” the maximum number of entries that can be returned. and listen, this part is not optional-optional: the entries array must be allocated to hold max_entries number of entries. no cap, allocate it properly or it's giving disaster 😭

🌈 DESCRIPTION 🌈

Returns the number of entries on success, or the appropriate error code. literally that's the whole description, she's short and to the point and we respect her for it ✨


πŸŽ€ SEE ALSO πŸŽ€


πŸ’€ friendly reminder that the entries array has to fit max_entries entries β€” that's a hard requirement, not a suggestion, okay? go allocate properly and slay 🫢

and that's the page!! 🌟 this one ships out of ./drivers/infiniband/core and it's dated October 2026 β€” mwah πŸ’‹ thanks for reading bestie, ily, go query those GID tables πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from