Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
We tend to rebase the rdma kernel subsystem every release, and the rdma userspace (and thus rdma-core) needs to be updated in sync with that. We're targeting 4.14 upstream kernel code for Red Hat Enterprise Linux 7.5, which means we need the latest rdma-core as well, so we're updating to v15.
Note: This release significantly changes how the rdma-core package loads RDMA modules. In particular, it enables kernel module autoloading instead of a static kernel module load via the rdma.service systemd service. This will need significant testing to make sure that the update doesn't break working systems.
(In reply to Doug Ledford from comment #5)
> Note: This release significantly changes how the rdma-core package loads
> RDMA modules. In particular, it enables kernel module autoloading instead
> of a static kernel module load via the rdma.service systemd service. This
> will need significant testing to make sure that the update doesn't break
> working systems.
Looks like there's a corresponding udev patch we'll need as well:
commit 5570d7f95612 ("Support 'rdma' as a ListenNetlink= argument (#6626)")
hardware/configurations supported:
-Broadcom NetXtreme-C and NetXtreme-E BCM573xx and BCM574xx 10/20/25/40/50/100 Gbps Ethernet Network Controllers
Setup, teardown, and any other configuration commands required to prepare for feature tests:
- Setup 2 hosts with Broadcom's adaptors
- Connection the link through Back to Back
- Make sure "yum groupinstall Infiniband" succeeds.
- Make sure bnxt_en.ko is loaded.
- Assign IP addresses to interfaces on both the hosts
- Make sure bnxt_re.ko is loaded.
- make sure rdma-core rpm is installed.
- ibv_devinfo should list bnxt_reX devices.
- Run following command(s) to verify functionality:
Server:
rping -s -d -v -a <ip of server bnxt interface>
Client:
rping -c -d -v -a <ip of server bnxt interface>
- Run other RDMA capable test tools like
ib_*_bw and ib_*_lat set of tools in RDMA_CM and socket mode to report bandwith and latency numbers.
Comment 16Andre Beausoleil
2017-12-21 15:42:47 UTC
*** Bug 1456544 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0954