IBV_SRQ_PINGPONG(1)

📦
version 65.0 · 2 versions
  • 65.0 · alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 15.1 · freebsd 14.5, freebsd 15.1
, in alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 ibv_srq_pingpong 💖

okay bestie, welcome to the manual page for ibv_srq_pingpong — it's a USER COMMAND and it lives in section 1, and honestly? it's giving "tiny chaos gremlin that tests your InfiniBand fabric." 🦋

✨ NAME ✨

ibv_srq_pingpong — simple InfiniBand shared receive queue test

🌸 SYNOPSIS 🌸

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

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

so there's two whole moods of this command, and yes, you're allowed to just... not pass a HOSTNAME. we love options. 💅

🎀 DESCRIPTION 🎀

bestie, this runs a simple ping-pong test over InfiniBand using the reliable connected (RC) transport. but here's the twist that makes it special: it uses multiple queue pairs (QPs) and a single shared receive queue (SRQ). multiple QPs, one SRQ, all vibing together. it's giving group project where only one person holds the snacks. ✨

💜 OPTIONS 💜

one bullet per flag, no skipping, no summarizing, we respect the full list in this house. 👑

  • -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)
  • -q, --num-qp=NUM — use NUM queue pairs for test (default 16)
  • -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 QPs (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

that's twelve options, we counted, we did not lose a single one, periodt. 🌈

🦋 SEE ALSO 🦋

go bother these siblings next, they're all family:

👑 AUTHORS 👑

Roland Dreier — <rolandd@cisco.com> 💖

💀 BUGS 💀

okay so, real talk, no cap, we have to be honest here because this is the important part:

The network synchronization between client and server instances is weak, and does not prevent incompatible options from being used on the two instances. The method used for retrieving work completions is not strictly correct, and race conditions may cause failures on some systems.

so like… it might be a little messy. 😭 not me warning you about actual race conditions. read that again before you blame yourself. it's not you, it's the synchronization. 🙈

and that's the whole page bestie!! this manual page came from libibverbs, and it's dated August 30, 2005 — yeah, 2005, it's vintage, it's an icon, it walked so we could run. 🧚 ty for reading, go ping some pongs, ily 💜

📦 where this page comes from