[NEW PORT] net/ucx: Unified Communication X for high-performance messaging

[rikka.goering_outlook.de]

Summary

UCX (Unified Communication X) is a high-performance communication framework
for modern HPC and data-intensive workloads. It provides low-latency,
high-bandwidth messaging and remote-memory-access primitives across a wide
range of transports, including shared memory, TCP/IP, and RDMA-capable
interconnects such as InfiniBand and RoCE (when supported by the platform).

UCX is commonly used as a communication substrate for MPI, OpenSHMEM, and
other distributed runtimes. It exposes a set of layered APIs (UCP/UCT/UCS/UCM)
to balance portability and performance while enabling optimized transport
selection, rendezvous protocols, and progress models.

PR: #292889

Test Plan

• make stage-qa [OK]
• make check-plist [OK]
• portlint -AC [OK]
• portclippy Makefile [OK]
• poudriere testport [OK]

[rikka.goering_outlook.de]

Updated port from v1.19.1 to v1.20.0

[michaelo]

net/ucx/Makefile

50

You can do this bravely in do-install phase, see devel/nexus2-oss/Makefile

[rikka.goering_outlook.de]

• Updated port to version 1.20.0
• net/ucx: adjusted port to review feedback
  • moved renaming of sample config file from post-stage to post-install

[michaelo]

net/ucx/Makefile

46

Is the config file conditionally available during the build or what is the reason for the if clause?

[rikka.goering_outlook.de]

Closing this revision following the resolution of the corresponding Bugzilla PR (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292889
).
As discussed there, the patches should be submitted upstream first to avoid maintaining a large downstream patchset. I will revisit this once upstream integration has progressed.

net/ucx/Makefile

46

You’re right — the file isn’t conditionally present; the if guard is unnecessary here. It was leftover from my local update/testing workflow where I was being defensive about the presence of the config during an upgrade. I’ll remove the conditional and do the rename/install unconditionally in the next revision.