linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: longli@microsoft.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 05/12] net: mana: Set the DMA device max page size
Date: Tue, 17 May 2022 11:59:49 -0300	[thread overview]
Message-ID: <20220517145949.GH63055@ziepe.ca> (raw)
In-Reply-To: <1652778276-2986-6-git-send-email-longli@linuxonhyperv.com>

On Tue, May 17, 2022 at 02:04:29AM -0700, longli@linuxonhyperv.com wrote:
> From: Long Li <longli@microsoft.com>
> 
> The system chooses default 64K page size if the device does not specify
> the max page size the device can handle for DMA. This do not work well
> when device is registering large chunk of memory in that a large page size
> is more efficient.
> 
> Set it to the maximum hardware supported page size.

For RDMA devices this should be set to the largest segment size an
ib_sge can take in when posting work. It should not be the page size
of MR. 2M is a weird number for that, are you sure it is right?

Jason

  reply	other threads:[~2022-05-17 14:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  9:04 [PATCH 00/12] Introduce Microsoft Azure Network Adapter (MANA) RDMA driver longli
2022-05-17  9:04 ` [PATCH 01/12] net: mana: Add support for auxiliary device longli
2022-05-19 18:58   ` kernel test robot
2022-05-17  9:04 ` [PATCH 02/12] net: mana: Record the physical address for doorbell page region longli
2022-05-17  9:04 ` [PATCH 03/12] net: mana: Handle vport sharing between devices longli
2022-05-17 15:19   ` Stephen Hemminger
2022-05-17 23:39     ` Long Li
2022-05-17  9:04 ` [PATCH 04/12] net: mana: Add functions for allocating doorbell page from GDMA longli
2022-05-17  9:04 ` [PATCH 05/12] net: mana: Set the DMA device max page size longli
2022-05-17 14:59   ` Jason Gunthorpe [this message]
2022-05-17 19:32     ` Long Li
2022-05-17 19:35       ` Jason Gunthorpe
2022-05-17 20:04         ` Long Li
2022-05-18  0:03           ` Jason Gunthorpe
2022-05-18  5:59             ` [EXTERNAL] " Ajay Sharma
2022-05-18 16:05               ` Jason Gunthorpe
2022-05-18 21:05                 ` Ajay Sharma
2022-05-18 23:11                   ` Jason Gunthorpe
2022-05-19  0:37                     ` Long Li
2022-05-17  9:04 ` [PATCH 06/12] net: mana: Define data structures for protection domain and memory registration longli
2022-05-17  9:04 ` [PATCH 07/12] net: mana: Export Work Queue functions for use by RDMA driver longli
2022-05-17  9:04 ` [PATCH 08/12] net: mana: Record port number in netdev longli
2022-05-17  9:04 ` [PATCH 09/12] net: mana: Move header files to a common location longli
2022-05-17 15:03   ` Jason Gunthorpe
2022-05-17 19:34     ` Long Li
2022-05-17  9:04 ` [PATCH 10/12] net: mana: Define max values for SGL entries longli
2022-05-17  9:04 ` [PATCH 11/12] net: mana: Define and process GDMA response code GDMA_STATUS_MORE_ENTRIES longli
2022-05-17  9:04 ` [PATCH 12/12] RDMA/mana_ib: Add a driver for Microsoft Azure Network Adapter longli
2022-05-17 15:24   ` Jason Gunthorpe
2022-05-19  5:57     ` Long Li
2022-05-19 12:49       ` Jason Gunthorpe
2022-05-19 17:50         ` Long Li
2022-05-17 23:40   ` kernel test robot
2022-05-18  1:14   ` kernel test robot
2022-05-19 21:42   ` kernel test robot

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=20220517145949.GH63055@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kuba@kernel.org \
    --cc=kys@microsoft.com \
    --cc=leon@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sthemmin@microsoft.com \
    --cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).