IBV_UD_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_UD_PINGPONG πŸ’–

okay bestie, welcome to the ibv_ud_pingpong page β€” that's section 1 of the user commands manual, and she's a lil InfiniBand UD transport test, no big deal πŸ’…


✨ NAME ✨

ibv_ud_pingpong β€” a simple InfiniBand UD transport test πŸ¦‹


🌸 SYNOPSIS 🌸

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

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

so like, you either give her a HOSTNAME and she's the client, or you give her nothing and she's just vibing as the server, periodt ✨


πŸ’œ DESCRIPTION πŸ’œ

Run a simple ping-pong test over InfiniBand via the unreliable datagram (UD) transport. that's it, that's the whole job. she pings, she pongs, she slays πŸ’–


πŸ‘‘ OPTIONS πŸ‘‘

  • -p, --port=PORT β€” use TCP port PORT for the initial synchronization (default 18515) πŸŽ€
  • -d, --ib-dev=DEVICE β€” use IB device DEVICE (default is the first device found, she's not picky) 🌈
  • -i, --ib-port=PORT β€” use IB port PORT (default port 1) πŸ’«
  • -s, --size=SIZE β€” ping-pong messages of size SIZE (default 2048) πŸ“
  • -r, --rx-depth=DEPTH β€” post DEPTH receives at a time (default 500) πŸ“₯
  • -n, --iters=ITERS β€” perform ITERS message exchanges (default 1000) πŸ”
  • -l, --sl=SL β€” send messages with service level SL (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 βœ…

🫢 SEE ALSO 🫢

ibv_rc_pingpong(1), ibv_uc_pingpong(1), ibv_srq_pingpong(1), ibv_xsrq_pingpong(1)

the whole pingpong friend group, honestly iconic πŸŽ€


🌟 AUTHORS 🌟

Roland Dreier β€” <rolandd@cisco.com> πŸ‘‘


πŸ’€ BUGS πŸ’€

the network synchronization between client and server instances is weak, and it does not prevent incompatible options from being used on the two instances. so like, if you and your bestie pass different options, she will simply not stop you, and that's a whole mess πŸ™ˆ

the method used for retrieving work completions is not strictly correct, and race conditions may cause failures on some systems. no cap, it's giving slightly unhinged. proceed with awareness πŸ’…


and that's the page!! brought to you by <b>libibverbs</b>, dated <b>August 30, 2005</b> β€” yes she's an elder but she still ate. mwah πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from