diff options
| author | Kashyap Desai <kashyap.desai@broadcom.com> | 2024-10-28 13:06:54 +0300 |
|---|---|---|
| committer | Leon Romanovsky <leon@kernel.org> | 2024-10-30 15:24:50 +0300 |
| commit | 808ca6de989c598bc5af1ae0ad971a66077efac0 (patch) | |
| tree | 5951b6884ca2291e32c61b7728c1b380266da0ba /tools/perf/scripts/python/parallel-perf.py | |
| parent | ea4c990fa9e19ffef0648e40c566b94ba5ab31be (diff) | |
| download | linux-808ca6de989c598bc5af1ae0ad971a66077efac0.tar.xz | |
RDMA/bnxt_re: Check cqe flags to know imm_data vs inv_irkey
Invalidate rkey is cpu endian and immediate data is in big endian format.
Both immediate data and invalidate the remote key returned by
HW is in little endian format.
While handling the commit in fixes tag, the difference between
immediate data and invalidate rkey endianness was not considered.
Without changes of this patch, Kernel ULP was failing while processing
inv_rkey.
dmesg log snippet -
nvme nvme0: Bogus remote invalidation for rkey 0x2000019Fix in this patch
Do endianness conversion based on completion queue entry flag.
Also, the HW completions are already converted to host endianness in
bnxt_qplib_cq_process_res_rc and bnxt_qplib_cq_process_res_ud and there
is no need to convert it again in bnxt_re_poll_cq. Modified the union to
hold the correct data type.
Fixes: 95b087f87b78 ("bnxt_re: Fix imm_data endianness")
Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com>
Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
Link: https://patch.msgid.link/1730110014-20755-1-git-send-email-selvin.xavier@broadcom.com
Signed-off-by: Leon Romanovsky <leon@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/parallel-perf.py')
0 files changed, 0 insertions, 0 deletions