IBV_UC_PINGPONG(1)

💖 ibv_uc_pingpong — bestie's guide to the InfiniBand UC ping-pong 💖

okay so. ibv_uc_pingpong is a lil program in the libibverbs family — and yes, it lives in section 1 of the manual, the user commands section, so it's a real executable you just... run. It's a simple InfiniBand UC transport test. That's the whole vibe. 💅

✨ NAME ✨

ibv_uc_pingpong — simple InfiniBand UC transport test 🦋

🌸 SYNOPSIS 🌸

ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size]
[-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] HOSTNAME

ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size]
[-r rx depth] [-n iters] [-l sl] [-e] [-g gid index]

notice there's two whole forms up there — one where you name a HOSTNAME and one where you don't. pick your fighter. ✌️

🎀 DESCRIPTION 🎀

Run a simple ping-pong test over InfiniBand via the unreliable connected (UC) transport. 🏓

That's it, that's the whole thing. You ping, you pong, you learn whether your UC path is actually slaying or not. ✨

💜 OPTIONS 💜

• -p, --port=PORT — use TCP port PORT for initial synchronization (default 18515) 🫶
• -d, --ib-dev=DEVICE — use IB device DEVICE (default: first device found) 👑
• -i, --ib-port=PORT — use IB port PORT (default: port 1) 🌈
• -s, --size=SIZE — ping-pong messages of size SIZE (default 4096) 💌
• -m, --mtu=SIZE — path MTU SIZE (default 1024) 📏
• -r, --rx-depth=DEPTH — post DEPTH receives at a time (default 1000) 🧺
• -n, --iters=ITERS — perform ITERS message exchanges (default 1000) 🔁
• -l, --sl=SL — use SL as the service level value of the QP (default 0) ⭐
• -e, --events — sleep while waiting for work completion events (default is to poll for completions) 😴
• -g, --gid-idx=GIDINDEX — local port GIDINDEX 🆔
• -c, --chk — validate received buffer ✅

heads up bestie: -c shows up in the OPTIONS list but not in the SYNOPSIS up there. that's just how the page is written. i'm not going to gaslight you about it, i'm just reporting it. 🙈

👀 SEE ALSO 👀

• ibv_rc_pingpong(1)
• ibv_ud_pingpong(1)
• ibv_srq_pingpong(1)
• ibv_xsrq_pingpong(1)

the whole ping-pong friend group. they're all iconic. 🫶

💀 AUTHORS 💀

Roland Dreier — <rolandd@cisco.com>

😭 BUGS 😭

okay so this is the part where we get real for a sec, no cap.

The network synchronization between client and server instances is weak, and does not prevent incompatible options from being used on the two instances.

And the method used for retrieving work completions is not strictly correct, and race conditions may cause failures on some systems.

fr fr, read that twice. weak sync, incompatible options can sneak through, and the completion-retrieval method is not strictly correct — race conditions can make this fail on some systems. it is what it is. 💅

and that's the page, bestie!! this one shipped as part of libibverbs, and the date on it is August 30, 2005 — yeah, it's been serving looks since 2005. periodt. 💖✨🎀🦋🌸