From: Bob Pearson <rpearsonhpe@gmail.com>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"mie@igel.co.jp" <mie@igel.co.jp>,
"bvanassche@acm.org" <bvanassche@acm.org>
Subject: Re: 回复: [PATCH for-rc v3 1/6] RDMA/rxe: Add memory barriers to kernel queues
Date: Tue, 14 Sep 2021 10:47:58 -0500 [thread overview]
Message-ID: <33765191-3b89-269e-c11c-08609f9c3e10@gmail.com> (raw)
In-Reply-To: <OS0PR01MB637135BAE66CD2DF3BDF6AE783DA9@OS0PR01MB6371.jpnprd01.prod.outlook.com>
On 9/14/21 1:04 AM, yangx.jy@fujitsu.com wrote:
> Hi Bob,
>
> Why do you want to use FROM_CLIENT and TO_CLIENT suffix?
> It seems readable to use FROM_USER and TO_USER suffix (i.e. between user space and kernel space).
>
> Best Regards,
> Xiao Yang
>
The whole purpose of this patch is to extend the memory barriers to support
user <-> kernel *and* kernel <-> kernel. Changing the name made it clearer
that it's not just user space. It also made it easier to make sure I had
gotten all of them changed/looked at. Now that is done, if everyone wants it
back to USER I could be talked into it.
Bob
next prev parent reply other threads:[~2021-09-14 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 20:44 [PATCH for-rc v3 0/6] RDMA/rxe: Various bug fixes Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 1/6] RDMA/rxe: Add memory barriers to kernel queues Bob Pearson
2021-09-10 1:19 ` Zhu Yanjun
2021-09-10 4:01 ` Bob Pearson
2021-09-14 6:04 ` 回复: " yangx.jy
2021-09-14 15:47 ` Bob Pearson [this message]
2021-09-09 20:44 ` [PATCH for-rc v3 2/6] RDMA/rxe: Fix memory allocation while locked Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 3/6] RDMA/rxe: Cleanup MR status and type enums Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 4/6] RDMA/rxe: Separate HW and SW l/rkeys Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 5/6] RDMA/rxe: Create duplicate mapping tables for FMRs Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 6/6] RDMA/rxe: Only allow invalidate for appropriate MRs Bob Pearson
2021-09-09 21:52 ` [PATCH for-rc v3 0/6] RDMA/rxe: Various bug fixes Bart Van Assche
2021-09-10 19:38 ` Pearson, Robert B
2021-09-10 20:23 ` Bart Van Assche
2021-09-10 21:16 ` Bob Pearson
2021-09-10 21:47 ` Bob Pearson
2021-09-10 21:50 ` Bob Pearson
2021-09-10 22:07 ` Bart Van Assche
2021-09-12 14:41 ` Bob Pearson
2021-09-14 3:26 ` Bart Van Assche
2021-09-14 4:18 ` Bob Pearson
2021-09-12 14:42 ` Bob Pearson
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=33765191-3b89-269e-c11c-08609f9c3e10@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mie@igel.co.jp \
--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).