From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Leon Romanovsky <leonro@nvidia.com>,
Bernard Metzler <BMT@zurich.ibm.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Pass a pointer to virt_to_page()
Date: Thu, 30 Mar 2023 09:06:23 -0300 [thread overview]
Message-ID: <ZCV7PwYwLVXGS202@nvidia.com> (raw)
In-Reply-To: <66639a8e-e8b8-64b4-5b04-dec357db86a8@gmail.com>
On Wed, Mar 29, 2023 at 09:45:45PM -0500, Bob Pearson wrote:
> On 3/29/23 18:16, Jason Gunthorpe wrote:
> > On Wed, Mar 29, 2023 at 04:28:08PM +0200, Linus Walleij wrote:
> >
> >> I'm a bit puzzled: could the above code (which exist in
> >> three instances in the driver) even work as it is? Or is it not used?
> >> Or is there some failover from DMA to something else that is constantly
> >> happening?
> >
> > The physical address dma type IB_MR_TYPE_DMA is rarely used and maybe
> > nobody ever tested it, at least in a configuration where kva != pa
> >
> > Then again, maybe I got it wrong and it is still a kva in this case
> > because it is still ultimately DMA mapped when using IB_MR_TYPE_DMA?
> >
> > Bob?
> >
> > Jason
>
> In the amd64 environment I use to dev and test there is no difference AFAIK.
> I have to go on faith that other platforms work but have very little experience.
Honestly, I would be much happier if the virtual wrappers used
physical not kva :\ But that is too much to ask
So I suspsect I got it wrong and it is a kva still
Jason
next prev parent reply other threads:[~2023-03-30 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:32 [PATCH] RDMA/rxe: Pass a pointer to virt_to_page() Linus Walleij
2023-03-24 12:27 ` kernel test robot
2023-03-24 13:59 ` Jason Gunthorpe
2023-03-29 14:28 ` Linus Walleij
2023-03-29 20:17 ` Bob Pearson
2023-03-29 23:16 ` Jason Gunthorpe
2023-03-30 2:45 ` Bob Pearson
2023-03-30 12:06 ` Jason Gunthorpe [this message]
2023-03-30 15:19 ` Linus Walleij
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=ZCV7PwYwLVXGS202@nvidia.com \
--to=jgg@nvidia.com \
--cc=BMT@zurich.ibm.com \
--cc=leonro@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.