From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: Jason Gunthorpe <jgg@ziepe.ca>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"aharonl@nvidia.com" <aharonl@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mbloch@nvidia.com" <mbloch@nvidia.com>,
"liweihang@huawei.com" <liweihang@huawei.com>,
"liangwenpeng@huawei.com" <liangwenpeng@huawei.com>,
"yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"y-goto@fujitsu.com" <y-goto@fujitsu.com>
Subject: Re: [RFC PATCH rdma-next 08/10] RDMA/rxe: Implement flush execution in responder side
Date: Thu, 6 Jan 2022 06:42:57 +0000 [thread overview]
Message-ID: <347eb51d-6b0c-75fb-e27f-6bf4969125fe@fujitsu.com> (raw)
In-Reply-To: <20220106002804.GS6467@ziepe.ca>
On 06/01/2022 08:28, Jason Gunthorpe wrote:
> On Tue, Dec 28, 2021 at 04:07:15PM +0800, Li Zhijian wrote:
>> + while (length > 0) {
>> + va = (u8 *)(uintptr_t)buf->addr + offset;
>> + bytes = buf->size - offset;
>> +
>> + if (bytes > length)
>> + bytes = length;
>> +
>> + arch_wb_cache_pmem(va, bytes);
> So why did we need to check that the va was pmem to call this?
Sorry, i didn't get you.
I didn't check whether va is pmem, since only MR registered with PERSISTENCE(only pmem can
register this access flag) can reach here.
Thanks
Zhijian
>
> Jason
next prev parent reply other threads:[~2022-01-06 6:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 8:07 [RFC PATCH rdma-next 00/10] RDMA/rxe: Add RDMA FLUSH operation Li Zhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 01/10] RDMA: mr: Introduce is_pmem Li Zhijian
2022-01-06 0:21 ` Jason Gunthorpe
2022-01-06 6:12 ` lizhijian
2022-01-14 8:10 ` Li, Zhijian
2022-01-27 22:30 ` Jeff Moyer
2022-01-16 18:11 ` Dan Williams
2022-01-18 8:55 ` lizhijian
2022-01-18 15:28 ` Dan Williams
2022-01-19 2:01 ` lizhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 02/10] RDMA: Allow registering MR with flush access flags Li Zhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 03/10] RDMA/rxe: Allow registering FLUSH flags for supported device only Li Zhijian
2022-01-06 0:22 ` Jason Gunthorpe
2022-01-06 6:20 ` lizhijian
2022-01-13 6:43 ` lizhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 04/10] RDMA/rxe: Enable IB_DEVICE_RDMA_FLUSH for rxe device Li Zhijian
2022-01-06 0:22 ` Jason Gunthorpe
2022-01-06 6:26 ` lizhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 05/10] RDMA/rxe: Allow registering persistent flag for pmem MR only Li Zhijian
2021-12-30 22:25 ` Tom Talpey
2021-12-31 3:34 ` lizhijian
2021-12-31 14:40 ` Tom Talpey
2022-01-04 1:32 ` lizhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 06/10] RDMA/rxe: Implement RC RDMA FLUSH service in requester side Li Zhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 07/10] RDMA/rxe: Set BTH's SE to zero for FLUSH packet Li Zhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 08/10] RDMA/rxe: Implement flush execution in responder side Li Zhijian
2021-12-30 22:18 ` Tom Talpey
2021-12-31 1:37 ` lizhijian
2021-12-31 2:32 ` Tom Talpey
2022-01-04 8:51 ` lizhijian
2022-01-04 16:02 ` Tom Talpey
2022-01-06 0:35 ` Jason Gunthorpe
2022-01-04 16:40 ` Tom Talpey
2022-01-05 1:43 ` lizhijian
2022-01-06 0:28 ` Jason Gunthorpe
2022-01-06 6:42 ` lizhijian [this message]
2022-01-06 17:33 ` Jason Gunthorpe
2022-01-10 5:45 ` lizhijian
2022-01-10 14:34 ` Jason Gunthorpe
2022-01-11 5:34 ` lizhijian
2022-01-11 20:48 ` Jason Gunthorpe
2022-01-12 9:50 ` lizhijian
2022-01-12 13:12 ` Jason Gunthorpe
2022-01-13 6:29 ` lizhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 09/10] RDMA/rxe: Implement flush completion Li Zhijian
2021-12-28 8:07 ` [RFC PATCH rdma-next 10/10] RDMA/rxe: Add RD FLUSH service support Li Zhijian
2021-12-29 8:49 ` [RFC PATCH rdma-next 00/10] RDMA/rxe: Add RDMA FLUSH operation Gromadzki, Tomasz
2021-12-29 14:35 ` Tom Talpey
2021-12-31 1:10 ` lizhijian
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=347eb51d-6b0c-75fb-e27f-6bf4969125fe@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=aharonl@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=liangwenpeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liweihang@huawei.com \
--cc=mbloch@nvidia.com \
--cc=rpearsonhpe@gmail.com \
--cc=y-goto@fujitsu.com \
--cc=yangx.jy@fujitsu.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).