dapl-utest(1)

πŸ“¦ version 2.1.10, in opensuse-leap 16.0

πŸ’… dapl-utest β€” the manual page, but make it make sense ✨

okay so bestie, welcome to dapl-utest(1) β€” it lives in the USER COMMANDS section and honestly? it's a whole vibe. it's the little test program that pokes at the uDAPL interfaces until they prove they work. let's get into it 🫢


✨ NAME ✨

dapl-utest β€” a simple uDAPL send/receive and RDMA test. that's it. that's the whole elevator pitch. πŸŽ€


🌸 SYNOPSIS 🌸

dapl-utest [-P provider] [-b buf size] [-B burst count][-v] [-c] [-p]
[-d] [-s]

dapl-utest [-P provider] [-b buf size] [-B burst count][-v] [-c] [-p]
[-d] [-h HOSTNAME]

two forms, one of them runs a server (-s), the other one takes a hostname (-h HOSTNAME) and goes client mode. pick your fighter πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so dapl-utest is a simple test used to exercise and verify the uDAPL interfaces. lowkey iconic of it.

the important part, bestie: you need at least two instantiations of the test running. one acts as the server, the other acts as the client. no solo runs, it's a two-player game fr fr. 😭

the server side of the test, once invoked, listens for connection requests, and it keeps doing that until timing out or killed. main character energy honestly β€” it just waits.

upon receipt of a cd connection request, the connection is established, and then the server and client sides exchange the information necessary to perform RDMA writes and reads. that's the whole plot. ✨


πŸ’– OPTIONS πŸ’–

  • -P=PROVIDER β€” use PROVIDER to specify the uDAPL interface using /etc/dat.conf. the default is ofa-v2-mlx4_0-1u. yes, that's the default, write it down πŸ“
  • -b=BUFFER_SIZE β€” use buffer size BUFFER_SIZE for RDMA. the default is 64.
  • -B=BURST_COUNT β€” use busrt count BURST_COUNT for interations. the default is 10. (yes, the manpage really says "busrt" and "interations" β€” we don't gatekeep spelling here, we gatekeep facts πŸ’€)
  • -v β€” verbose output. default is off.
  • -c β€” use consumer notification events. default is off.
  • -p β€” use polling. (the default is to wait for event, so -p is you choosing violence πŸ”₯)
  • -d β€” delay in seconds before close. default is off.
  • -s β€” run as server. and yes, the default is literally listed as - run as server, so the default already runs as server. slay.
  • -h=HOSTNAME β€” use HOSTNAME to specify server hostname or IP address. the default is none.

🌈 EXAMPLES 🌈

okay these two are the ones you'll actually type, so:

dapl-utest -P OpenIB-cma -v -s

starts a server process with debug verbosity using provider OpenIB-cma. she's loud and she's listening πŸ‘‘

dapl-utest -P OpenIB-cma -h server1-ib0

starts a client process, using the OpenIB-cma provider to connect to hostname server1-ib0. go get your server bestie πŸƒβ€β™€οΈπŸ’¨


πŸŽ€ SEE ALSO πŸŽ€

the whole friend group, no cap:


πŸ‘‘ AUTHORS πŸ‘‘

Arlin Davis β€” <arlin.r.davis@intel.com> 🫢


that's the page!! this one ships as uDAPL 2.1, dated November 15, 2016 β€” vintage but still serving πŸ’œβœ¨ go forth and test those RDMA reads and writes, bestie, and remember: two instantiations minimum, periodt πŸ’…

πŸ“¦ where this page comes from