From: Jason Gunthorpe <jgg@nvidia.com>
To: Cheng Xu <chengyou@linux.alibaba.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, KaiShen@linux.alibaba.com
Subject: Re: [PATCH for-next v2 1/2] RDMA/erdma: Use fixed hardware page size
Date: Fri, 24 Mar 2023 11:34:22 -0300 [thread overview]
Message-ID: <ZB207tLHgpnRjDff@nvidia.com> (raw)
In-Reply-To: <20230307102924.70577-2-chengyou@linux.alibaba.com>
On Tue, Mar 07, 2023 at 06:29:23PM +0800, Cheng Xu wrote:
> Hardware's page size is 4096, but the kernel's page size may vary. Driver
> should use hardware's page size when communicating with hardware.
>
> Fixes: 155055771704 ("RDMA/erdma: Add verbs implementation")
> Signed-off-by: Cheng Xu <chengyou@linux.alibaba.com>
> ---
> drivers/infiniband/hw/erdma/erdma_hw.h | 4 ++++
> drivers/infiniband/hw/erdma/erdma_verbs.c | 17 +++++++++--------
> 2 files changed, 13 insertions(+), 8 deletions(-)
This patch applied to for-next
Thanks,
Jason
next prev parent reply other threads:[~2023-03-24 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:29 [PATCH for-next v2 0/2] RDMA/erdma: Add non-4K page size support Cheng Xu
2023-03-07 10:29 ` [PATCH for-next v2 1/2] RDMA/erdma: Use fixed hardware page size Cheng Xu
2023-03-24 14:34 ` Jason Gunthorpe [this message]
2023-03-07 10:29 ` [PATCH for-next v2 2/2] RDMA/erdma: Support non-4K page size in doorbell allocation Cheng Xu
2023-03-14 10:23 ` Leon Romanovsky
[not found] ` <5b0cc34d-a185-d9b4-c312-27bc959d929d@linux.alibaba.com>
2023-03-14 11:34 ` Cheng Xu
2023-03-14 11:50 ` Cheng Xu
2023-03-14 14:10 ` Leon Romanovsky
2023-03-15 1:58 ` Cheng Xu
2023-03-15 10:22 ` Leon Romanovsky
2023-03-21 14:30 ` Jason Gunthorpe
2023-03-22 7:05 ` Cheng Xu
2023-03-22 11:54 ` Jason Gunthorpe
2023-03-22 13:30 ` Cheng Xu
2023-03-22 14:01 ` Jason Gunthorpe
2023-03-22 15:09 ` Gal Pressman
2023-03-23 6:57 ` Cheng Xu
2023-03-23 11:53 ` Jason Gunthorpe
2023-03-23 12:33 ` Cheng Xu
2023-03-23 13:05 ` Jason Gunthorpe
2023-03-23 14:10 ` Cheng Xu
2023-03-23 14:18 ` Jason Gunthorpe
2023-03-26 0:10 ` Cheng Xu
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=ZB207tLHgpnRjDff@nvidia.com \
--to=jgg@nvidia.com \
--cc=KaiShen@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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