RCOPY(1)

πŸŽ€ NAME πŸŽ€

rcopy β€” simple file copy over RDMA.

This page is from the librdmacm manual, bestie. It’s the RCOPY(1) page. Okay so, let’s get into it. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

rcopy source server[:destination] [-p port]
rcopy [-p port]

πŸ’… DESCRIPTION πŸ’…

It uses sockets over RDMA interface to copy a source file to the specified destination. Periodt. ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • source β€” the name and path of the source file to copy. Like, the file you’re sending, bestie. πŸŽ€
  • server β€” the name or address of the destination server. That’s where it’s going. πŸ¦‹
  • :destination β€” an optional destination filename and path. If not given, the destination filename will match that of the source. So if you skip it, it’s giving same-name energy. πŸ’…
  • -p server_port β€” the server's port number. That’s the port, no cap. πŸ”₯

πŸ’– NOTES πŸ’–

Basic usage is to start rcopy on a server system, then run rcopy sourcefile servername. The server application will continue to run after copying the file, but is currently single-threaded. So yeah, one thing at a time, bestie. 😭

Because this test maps RDMA resources to userspace, users must ensure that they have available system resources and permissions. See the libibverbs README file for additional details. Don’t skip that, fr fr. 🫢


🌈 SEE ALSO 🌈

  • rdma_cm(7) β€” go read that too, iykyk. πŸ‘‘

That’s the whole vibe, bestie. This page is from librdmacm, dated 2011-12-2, and it’s the RCOPY(1) page. Slay. πŸ’…βœ¨

πŸ“¦ where this page comes from