[Feature]: Improved Broadcom NIC support

[Bellk17]

Suggestion Description

Currently, AMD’s official ROCm container images provide limited support for bnxt modules. This has been a friction point for customers who are used to base images working out-of-the-box on the Nvidia side with Mellanox.

Current setup docs:
https://rocm.docs.amd.com/en/latest/how-to/rocm-for-ai/system-setup/multi-node-setup.html

This limits the usability of ROCm base containers for distributed workloads, as users must manually install and configure bnxt drivers or rebuild container images to support RoCE, which can require additional CI work to support different deployments.

We understand that supporting multiple RoCE implementations (Broadcom, etc.) may be non-trivial. However, even partial out-of-the-box support or the ability to select the target version via an ENV would significantly improve the usability and portability of ROCm containers for multi-node workloads.

Operating System

No response

GPU

No response

ROCm Component

No response

[Bellk17]

Here is example snippet from Dockerfile that would ideally be avoided.

COPY ${HOST_BNXT_PATH}/libbnxt_re-${BNXT_VER}.tar.gz /tmp/
RUN tar xzf /tmp/libbnxt_re-${BNXT_VER}.tar.gz -C /tmp/
RUN mv /usr/lib/x86_64-linux-gnu/libibverbs/libbnxt_re-rdmav34.so /usr/lib/x86_64-linux-gnu/libibverbs/libbnxt_re-rdmav34.so.inbox
RUN cd /tmp/libbnxt_re-${BNXT_VER}/ && sh ./autogen.sh && ./configure
RUN make -C /tmp/libbnxt_re-${BNXT_VER} clean all install
RUN echo '/usr/local/lib' > /etc/ld.so.conf.d/libbnxt_re.conf
RUN ldconfig