linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	"david.marchand@6wind.com" <david.marchand@6wind.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
	"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Subject: Re: [PATCH] RDMA/rxe: Check the last packet by RXE_END_MASK
Date: Tue, 11 Jan 2022 22:42:12 +0800	[thread overview]
Message-ID: <9e75da26-1339-36d4-1e30-83046b53e138@linux.dev> (raw)
In-Reply-To: <61DBC15E.5000402@fujitsu.com>


在 2022/1/10 13:17, yangx.jy@fujitsu.com 写道:
> On 2022/1/7 19:49, Yanjun Zhu wrote:
>> It seems that it does not mean to check the last packet. It means that
>> it receives a MSN response.
> Hi Yanjun,
>
> Checking the last packet is a way to indicate that responder has
> completed an entire request(including multiple packets) and then
> increases a msn.

Hi, Xiao

What does the msn mean?

Thanks a lot.

Zhu Yanjun

>
> Best Regards,
> Xiao Yang

  reply	other threads:[~2022-01-11 14:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  3:44 [PATCH] RDMA/rxe: Check the last packet by RXE_END_MASK Xiao Yang
2022-01-06  0:40 ` Jason Gunthorpe
2022-01-06 19:55   ` Robert Pearson
2022-01-07 11:49   ` Yanjun Zhu
2022-01-10  5:17     ` yangx.jy
2022-01-11 14:42       ` Yanjun Zhu [this message]
2022-01-11 15:16         ` Haakon Bugge
2022-01-12  1:19           ` Yanjun Zhu
2022-01-12  3:58             ` yangx.jy
2022-01-15  3:38               ` Yanjun Zhu
2022-01-18  2:20                 ` yangx.jy
2022-01-19 14:08                   ` Yanjun Zhu
2022-01-20  9:33                     ` yangx.jy
2022-01-21 13:18                       ` Yanjun Zhu
2022-02-08 16:40 ` 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=9e75da26-1339-36d4-1e30-83046b53e138@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=david.marchand@6wind.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yangx.jy@fujitsu.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;
as well as URLs for NNTP newsgroup(s).