RPMA_UTILS_IBV_CONTEXT_IS_ODP_CAPABLE(3)

📦
version 1.3.0 · 3 versions
, in ubuntu noble

💖 rpma_utils_ibv_context_is_odp_capable — RPMA Programmer's Manual (yes bestie, section 3) 💖

okay so real talk, this whole page lives in the RPMA Programmer's Manual, and it's all about one lil function with a very long name that asks a very simple question: does your RDMA device do On-Demand Paging or not? 🦋

✨ NAME ✨

rpma_utils_ibv_context_is_odp_capable — is On-Demand Paging supported 💅

🌸 SYNOPSIS 🌸

#include <librpma.h>

struct ibv_context;
int rpma_utils_ibv_context_is_odp_capable(struct ibv_context *ibv_ctx,
        int *is_odp_capable);

🎀 DESCRIPTION 🎀

okay so here's the tea ☕ — rpma_utils_ibv_context_is_odp_capable() goes and queries the RDMA device context's capabilities and then checks whether it actually supports On-Demand Paging. that's it. that's the whole vibe check. 🫶

🔥 RETURN VALUE 🔥

  • 0 on success — slay, it worked 💖
  • a negative error code on failure — not slay 😭
⚠️ and listen, if it fails, the value sitting in *is_odp_capable is undefined. don't trust it. don't look at it. it's giving chaos. 💀

💜 ERRORS 💜

rpma_utils_ibv_context_is_odp_capable() can fail with these, bestie:

  • RPMA_E_INVAL — ibv_ctx or is_odp_capable is NULL 🙈 like, you gotta actually pass something, girl
  • RPMA_E_PROVIDER — ibv_query_device_ex() failed, and the exact cause of the error can be read from the log 👑 (go check the log, iykyk)

🌈 SEE ALSO 🌈

and that's the whole page, periodt ✨ this lil gem is from the RPMA project, version dated 01 April 2024 — so yeah, go query those capabilities and stay iconic 💅🎀🦋

📦 where this page comes from