Bug 2064298
| Summary: | [RHEL8.6] various number benchmarks fail on mlx4 IB/RoCE devices | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Brian Chae <bchae> |
| Component: | mvapich2 | Assignee: | Kamal Heib <kheib> |
| Status: | ASSIGNED --- | QA Contact: | Infiniband QE <infiniband-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.6 | CC: | hwkernel-mgr, kheib, rdma-dev-team |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2026666 | ||
|
Description
Brian Chae
2022-03-15 14:06:06 UTC
On RHEL9.3, the similar mvapich2 benchmark failures were observed on MLX5 RoCE devices - especially on MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro ] An example failure: + [23-07-21 10:05:22] timeout --preserve-status --kill-after=5m 3m mpirun -hostfile /root/hfile_one_core -np 2 mpitests-IMB-MPI1 Sendrecv -time 1.5 [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][rdma_param_handle_heterogeneity] All nodes involved in the job were detected to be homogeneous in terms of processors and interconnects. Setting MV2_HOMOGENEOUS_CLUSTER=1 can improve job startup performance on such systems. The following link has more details on enhancing job startup performance. http://mvapich.cse.ohio-state.edu/performance/job-startup/. [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][rdma_param_handle_heterogeneity] To suppress this warning, please set MV2_SUPPRESS_JOB_STARTUP_PERFORMANCE_WARNING to 1 #---------------------------------------------------------------- # Intel(R) MPI Benchmarks 2021.3, MPI-1 part #---------------------------------------------------------------- # Date : Fri Jul 21 10:05:23 2023 # Machine : x86_64 # System : Linux # Release : 5.14.0-339.el9.x86_64 # Version : #1 SMP PREEMPT_DYNAMIC Thu Jul 13 07:33:32 EDT 2023 # MPI Version : 3.1 # MPI Thread Environment: # Calling sequence was: # mpitests-IMB-MPI1 Sendrecv -time 1.5 # Minimum message length in bytes: 0 # Maximum message length in bytes: 4194304 # # MPI_Datatype : MPI_BYTE # MPI_Datatype for reductions : MPI_FLOAT # MPI_Op : MPI_SUM # # # List of Benchmarks to run: # Sendrecv #----------------------------------------------------------------------------- # Benchmarking Sendrecv # #processes = 2 #----------------------------------------------------------------------------- #bytes #repetitions t_min[usec] t_max[usec] t_avg[usec] Mbytes/sec 0 1000 1.97 1.98 1.97 0.00 1 1000 2.05 2.05 2.05 0.97 2 1000 2.07 2.07 2.07 1.93 4 1000 2.05 2.05 2.05 3.91 8 1000 2.05 2.05 2.05 7.79 16 1000 2.07 2.07 2.07 15.43 32 1000 2.10 2.10 2.10 30.52 64 1000 2.12 2.13 2.12 60.09 128 1000 2.23 2.23 2.23 114.58 256 1000 3.29 3.29 3.29 155.74 512 1000 3.39 3.39 3.39 301.85 1024 1000 3.83 3.83 3.83 535.03 2048 1000 4.76 4.77 4.76 859.51 [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][handle_cqe] Send desc error in msg to 1, wc_opcode=0 [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][handle_cqe] Msg from 1: wc.status=12 (transport retry counter exceeded), wc.wr_id=0x5627244dbae0, wc.opcode=0, vbuf->phead->type=0 = MPIDI_CH3_PKT_EAGER_SEND [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][mv2_print_wc_status_error] IBV_WC_RETRY_EXC_ERR: This event is generated when a sender is unable to receive feedback from the receiver. This means that either the receiver just never ACKs sender messages in a specified time period, or it has been disconnected or it is in a bad state which prevents it from responding. If this happens when sending the first message, usually it means that the QP connection attributes are wrong or the remote side is not in a state that it can respond to messages. If this happens after sending the first message, usually it means that the remote QP is not available anymore or that there is congestion in the network preventing the packets from reaching on time. Relevant to: RC or DC QPs. [rdma-perf-00.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][handle_cqe] src/mpid/ch3/channels/mrail/src/gen2/ibv_channel_manager.c:497: [] Got completion with error 12, vendor code=0x81, dest rank=1 : Cannot allocate memory (12) [rdma-perf-01.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][handle_cqe] Send desc error in msg to 0, wc_opcode=0 [rdma-perf-01.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][handle_cqe] Msg from 0: wc.status=12 (transport retry counter exceeded), wc.wr_id=0x558f8e40c050, wc.opcode=0, vbuf->phead->type=0 = MPIDI_CH3_PKT_EAGER_SEND [rdma-perf-01.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][mv2_print_wc_status_error] IBV_WC_RETRY_EXC_ERR: This event is generated when a sender is unable to receive feedback from the receiver. This means that either the receiver just never ACKs sender messages in a specified time period, or it has been disconnected or it is in a bad state which prevents it from responding. If this happens when sending the first message, usually it means that the QP connection attributes are wrong or the remote side is not in a state that it can respond to messages. If this happens after sending the first message, usually it means that the remote QP is not available anymore or that there is congestion in the network preventing the packets from reaching on time. Relevant to: RC or DC QPs. [rdma-perf-01.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][handle_cqe] src/mpid/ch3/channels/mrail/src/gen2/ibv_channel_manager.c:497: [] Got completion with error 12, vendor code=0x81, dest rank=0 : Cannot allocate memory (12) + [23-07-21 10:06:22] __MPI_check_result 252 mpitests-mvapich2 IMB-MPI1 Sendrecv mpirun /root/hfile_one_core |