From: Jason Gunthorpe <jgg@nvidia.com>
To: "Yang, Xiao/杨 晓" <yangx.jy@fujitsu.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Subject: Re: [RESEND PATCH v5 1/2] RDMA/rxe: Support RDMA Atomic Write operation
Date: Mon, 24 Oct 2022 14:02:19 -0300 [thread overview]
Message-ID: <Y1bFG/OM5zSOoWcr@nvidia.com> (raw)
In-Reply-To: <ae0ec888-a509-5e79-2449-69a379d6dc16@fujitsu.com>
On Thu, Oct 20, 2022 at 09:25:46PM +0800, Yang, Xiao/杨 晓 wrote:
> On 2022/10/15 0:00, Jason Gunthorpe wrote:
> > People have been thinking of new uses for kmap, rxe still should be
> > calling it.
>
> Hi Jason,
>
> Thanks a lot for your reply.
> Could you tell me what is the new usage about kmap()?
New in-kernel memory protection schemes
> > The above just explains why it doesn't fail today, it doesn't excuse
> > the wrong usage.
>
> I wonder why we need to use kmap() in this case?
> I'm sorry to ask the stupid question.
It is the defined API to convert a struct page into an address the CPU
can access.
Jason
next prev parent reply other threads:[~2022-10-24 18:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 4:02 [RESEND PATCH v5 0/2] RDMA/rxe: Add RDMA Atomic Write operation yangx.jy
2022-07-08 4:02 ` [RESEND PATCH v5 1/2] RDMA/rxe: Support " yangx.jy
2022-09-23 22:22 ` Jason Gunthorpe
2022-09-26 6:55 ` Yang, Xiao/杨 晓
2022-10-06 7:53 ` Yang, Xiao/杨 晓
2022-10-14 16:00 ` Jason Gunthorpe
2022-10-20 13:25 ` Yang, Xiao/杨 晓
2022-10-24 17:02 ` Jason Gunthorpe [this message]
2022-09-27 8:18 ` Li Zhijian
2022-09-27 13:17 ` Jason Gunthorpe
2022-09-29 3:58 ` Yang, Xiao/杨 晓
2022-09-29 5:36 ` Yang, Xiao/杨 晓
2022-07-08 4:02 ` [RESEND PATCH v5 2/2] RDMA/rxe: Add RDMA Atomic Write attribute for rxe device yangx.jy
2022-08-04 7:30 ` [RESEND PATCH v5 0/2] RDMA/rxe: Add RDMA Atomic Write operation yangx.jy
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=Y1bFG/OM5zSOoWcr@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.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