From: longli@linuxonhyperv.com
To: "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>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
edumazet@google.com, shiraz.saleem@intel.com,
Ajay Sharma <sharmaajay@microsoft.com>
Cc: linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Long Li <longli@microsoft.com>
Subject: [Patch v6 05/12] net: mana: Set the DMA device max segment size
Date: Tue, 20 Sep 2022 18:22:25 -0700 [thread overview]
Message-ID: <1663723352-598-6-git-send-email-longli@linuxonhyperv.com> (raw)
In-Reply-To: <1663723352-598-1-git-send-email-longli@linuxonhyperv.com>
From: Ajay Sharma <sharmaajay@microsoft.com>
MANA hardware doesn't have any restrictions on the DMA segment size, set it
to the max allowed value.
Signed-off-by: Ajay Sharma <sharmaajay@microsoft.com>
Reviewed-by: Dexuan Cui <decui@microsoft.com>
Signed-off-by: Long Li <longli@microsoft.com>
Acked-by: Haiyang Zhang <haiyangz@microsoft.com>
---
Change log:
v2: Use the max allowed value as the hardware doesn't have any limit
drivers/net/ethernet/microsoft/mana/gdma_main.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/ethernet/microsoft/mana/gdma_main.c b/drivers/net/ethernet/microsoft/mana/gdma_main.c
index 63544ca9e238..b44548136027 100644
--- a/drivers/net/ethernet/microsoft/mana/gdma_main.c
+++ b/drivers/net/ethernet/microsoft/mana/gdma_main.c
@@ -1419,6 +1419,12 @@ static int mana_gd_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
if (err)
goto release_region;
+ err = dma_set_max_seg_size(&pdev->dev, UINT_MAX);
+ if (err) {
+ dev_err(&pdev->dev, "Failed to set dma device segment size\n");
+ goto release_region;
+ }
+
err = -ENOMEM;
gc = vzalloc(sizeof(*gc));
if (!gc)
--
2.17.1
next prev parent reply other threads:[~2022-09-21 1:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 1:22 [Patch v6 00/12] Introduce Microsoft Azure Network Adapter (MANA) RDMA driver longli
2022-09-21 1:22 ` [Patch v6 01/12] net: mana: Add support for auxiliary device longli
2022-09-21 1:22 ` [Patch v6 02/12] net: mana: Record the physical address for doorbell page region longli
2022-09-21 1:22 ` [Patch v6 03/12] net: mana: Handle vport sharing between devices longli
2022-09-21 1:22 ` [Patch v6 04/12] net: mana: Add functions for allocating doorbell page from GDMA longli
2022-09-21 1:22 ` longli [this message]
2022-09-21 1:22 ` [Patch v6 06/12] net: mana: Export Work Queue functions for use by RDMA driver longli
2022-09-21 1:22 ` [Patch v6 07/12] net: mana: Record port number in netdev longli
2022-09-21 1:22 ` [Patch v6 08/12] net: mana: Move header files to a common location longli
2022-09-21 1:22 ` [Patch v6 09/12] net: mana: Define max values for SGL entries longli
2022-09-21 1:22 ` [Patch v6 10/12] net: mana: Define and process GDMA response code GDMA_STATUS_MORE_ENTRIES longli
2022-09-21 1:22 ` [Patch v6 11/12] net: mana: Define data structures for protection domain and memory registration longli
2022-09-21 1:22 ` [Patch v6 12/12] RDMA/mana_ib: Add a driver for Microsoft Azure Network Adapter longli
2022-09-21 16:26 ` Jason Gunthorpe
2022-09-21 21:00 ` Long Li
2022-09-21 17:59 ` Jason Gunthorpe
2022-09-22 8:23 ` Long Li
2022-09-21 16:25 ` [Patch v6 00/12] Introduce Microsoft Azure Network Adapter (MANA) RDMA driver Jason Gunthorpe
2022-09-21 18:53 ` Long Li
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=1663723352-598-6-git-send-email-longli@linuxonhyperv.com \
--to=longli@linuxonhyperv.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--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=sharmaajay@microsoft.com \
--cc=shiraz.saleem@intel.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).