public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: zhenwei pi <pizhenwei@bytedance.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: zyjzyj2000@gmail.com, jgg@nvidia.com, leonro@nvidia.com
Subject: Re: [PATCH 3/3] RDMA/rxe: Fix __bth_set_resv6a
Date: Thu, 22 Aug 2024 20:37:36 +0800	[thread overview]
Message-ID: <8b3ca8f8-7e08-4ced-9f95-23130fafb9a1@linux.dev> (raw)
In-Reply-To: <20240822065223.1117056-4-pizhenwei@bytedance.com>

在 2024/8/22 14:52, zhenwei pi 写道:
> __bth_set_resv6a is used to clear BIT [24, 29] of rxe_bth::qpn, the
> wrong expression leads other BITs into 1.

 From the spec
"
9.2.11 RESERVE 6(RESV6) - 6 BITS
Reserved (variant) - 6 bits. Transmitted as 0, ignored on receive. This 
field
is not included in the invariant CRC.
C9-6: When generating a packet, the sender shall set the Resv6, F/Res1
and B/Res1 fields to zero. In general, the receiver shall ignore the 
reserved
fields.
"
I agree with you.
Thanks a lot.

Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>

Zhu Yanjun
> 
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
>   drivers/infiniband/sw/rxe/rxe_hdr.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe_hdr.h b/drivers/infiniband/sw/rxe/rxe_hdr.h
> index 46f82b27fcd2..1f0322491d8c 100644
> --- a/drivers/infiniband/sw/rxe/rxe_hdr.h
> +++ b/drivers/infiniband/sw/rxe/rxe_hdr.h
> @@ -234,7 +234,7 @@ static inline void __bth_set_resv6a(void *arg)
>   {
>   	struct rxe_bth *bth = arg;
>   
> -	bth->qpn = cpu_to_be32(~BTH_RESV6A_MASK);
> +	bth->qpn &= cpu_to_be32(~BTH_RESV6A_MASK);
>   }
>   
>   static inline int __bth_ack(void *arg)


  reply	other threads:[~2024-08-22 12:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  6:52 [PATCH 0/3] RDMA/rxe misc fixes zhenwei pi
2024-08-22  6:52 ` [PATCH 1/3] RDMA/rxe: Use sizeof instead of hard code number zhenwei pi
2024-08-22 11:59   ` Zhu Yanjun
2024-08-22 12:36     ` Jason Gunthorpe
     [not found]       ` <CABoGonKvG9AyuVPMG29b3q5bGr7ZAH5RsGg7TOtkcaAZm9F-Dg@mail.gmail.com>
2024-08-23  5:56         ` Zhu Yanjun
2024-08-23  8:23           ` zhenwei pi
2024-08-23  9:17             ` Zhu Yanjun
2024-08-22  6:52 ` [PATCH 2/3] RDMA/rxe: Typo fix zhenwei pi
2024-08-22 12:01   ` Zhu Yanjun
2024-08-22  6:52 ` [PATCH 3/3] RDMA/rxe: Fix __bth_set_resv6a zhenwei pi
2024-08-22 12:37   ` Zhu Yanjun [this message]
2024-08-23 14:44 ` [PATCH 0/3] RDMA/rxe misc fixes Jason Gunthorpe

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=8b3ca8f8-7e08-4ced-9f95-23130fafb9a1@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pizhenwei@bytedance.com \
    --cc=zyjzyj2000@gmail.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