public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Wang <jinpu.wang@ionos.com>
To: linux-rdma@vger.kernel.org
Cc: bvanassche@acm.org, leon@kernel.org, jgg@ziepe.ca,
	selvin.xavier@broadcom.com, haris.iqbal@ionos.com,
	jinpu.wang@ionos.com
Subject: [PATCH for-next 0/2] Fix for bnxt_re endianness issue
Date: Tue,  9 Jul 2024 17:01:17 +0200	[thread overview]
Message-ID: <20240709150119.29937-1-jinpu.wang@ionos.com> (raw)

We have found an issue when map a RNBD device between MLX and BCM nics.
When map a device between servers with MLX and BCM RoCE nics, RTRS
server complain about unknown imm type, and can't map the device,

The problem is bnxt_re do not handle endianness correctly in some cases,
hence this small patchset.

I tested it between BCM RoCE nics, also BCM and MLX NiCs for RNBD traffic.

Please review and consider for next release, the bug exists since the
beginning of bnxt_re.

Jack Wang (2):
  bnxt_re: Fix imm_data endianness
  bnxt_re: Fix inv_key endianness

 drivers/infiniband/hw/bnxt_re/ib_verbs.c | 14 +++++++-------
 drivers/infiniband/hw/bnxt_re/qplib_fp.h | 12 ++++++------
 2 files changed, 13 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-07-09 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 15:01 Jack Wang [this message]
2024-07-09 15:01 ` [PATCH for-next 1/2] bnxt_re: Fix imm_data endianness Jack Wang
2024-07-10  8:27   ` Selvin Xavier
2024-07-10  8:49     ` Jinpu Wang
2024-07-10  9:30     ` Jinpu Wang
2024-07-09 15:01 ` [PATCH for-next 2/2] bnxt_re: Fix inv_key endianness Jack Wang
2024-07-11  3:08   ` Greg Sword

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240709150119.29937-1-jinpu.wang@ionos.com \
    --to=jinpu.wang@ionos.com \
    --cc=bvanassche@acm.org \
    --cc=haris.iqbal@ionos.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=selvin.xavier@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox