From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH v2] providers/rxe: Set the correct value of resid for inline data
Date: Fri, 3 Sep 2021 01:39:23 +0000 [thread overview]
Message-ID: <61317CC6.1070406@fujitsu.com> (raw)
In-Reply-To: <819eadbd-9f9d-669f-a552-18a9e434a43a@gmail.com>
On 2021/9/3 3:48, Bob Pearson wrote:
> Hi,
>
> What are you looking for? I reviewed the patch (above) and agree with you that it makes sense.
> But it's not up to me to accept it. That would be Jason or Zhu.
Hi Bob,
Sorry for missing your review. Thanks for your remind.
> BTW until this is fixed I it looks like inline WRs are broken for the extended QP API.
I wonder if there is some commands or tests can verify new inline WRs in
rdma-core?
Best Regards,
Xiao Yang
> Bob
next prev parent reply other threads:[~2021-09-03 1:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 15:07 [PATCH v2] providers/rxe: Set the correct value of resid for inline data Xiao Yang
2021-08-10 3:40 ` Zhu Yanjun
2021-08-10 16:33 ` yangx.jy
2021-08-16 7:47 ` Zhu Yanjun
2021-08-17 0:54 ` yangx.jy
2021-08-23 2:44 ` Zhu Yanjun
2021-08-23 3:58 ` yangx.jy
2021-08-13 22:11 ` Bob Pearson
2021-08-16 3:55 ` Zhu Yanjun
2021-08-16 18:52 ` Bob Pearson
2021-08-23 1:33 ` yangx.jy
2021-08-25 9:44 ` Leon Romanovsky
2021-09-02 8:27 ` yangx.jy
2021-09-02 19:48 ` Bob Pearson
2021-09-03 1:39 ` yangx.jy [this message]
2021-09-03 3:34 ` Zhu Yanjun
2021-09-26 10:51 ` Leon Romanovsky
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=61317CC6.1070406@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.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;
as well as URLs for NNTP newsgroup(s).