From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: tsbogend@alpha.franken.de, olek2@wp.pl, hauke@hauke-m.de,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 1/3] MIPS: lantiq: dma: increase descritor count
Date: Tue, 4 Jan 2022 16:11:42 +0100 [thread overview]
Message-ID: <20220104151144.181736-2-olek2@wp.pl> (raw)
In-Reply-To: <20220104151144.181736-1-olek2@wp.pl>
NAT Performance results on BT Home Hub 5A (kernel 5.10.89, mtu 1500):
Down Up
Before 539 Mbps 599 Mbps
After 545 Mbps 625 Mbps
Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
---
arch/mips/include/asm/mach-lantiq/xway/xway_dma.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/include/asm/mach-lantiq/xway/xway_dma.h b/arch/mips/include/asm/mach-lantiq/xway/xway_dma.h
index 31ca9151b539..3dee15c61c8a 100644
--- a/arch/mips/include/asm/mach-lantiq/xway/xway_dma.h
+++ b/arch/mips/include/asm/mach-lantiq/xway/xway_dma.h
@@ -8,7 +8,7 @@
#define LTQ_DMA_H__
#define LTQ_DESC_SIZE 0x08 /* each descriptor is 64bit */
-#define LTQ_DESC_NUM 0x40 /* 64 descriptors / channel */
+#define LTQ_DESC_NUM 0xC0 /* 192 descriptors / channel */
#define LTQ_DMA_OWN BIT(31) /* owner bit */
#define LTQ_DMA_C BIT(30) /* complete bit */
--
2.30.2
next prev parent reply other threads:[~2022-01-04 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 15:11 [PATCH net-next 0/3] net: lantiq_xrx200: improve ethernet performance Aleksander Jan Bajkowski
2022-01-04 15:11 ` Aleksander Jan Bajkowski [this message]
2022-01-04 15:11 ` [PATCH net-next 2/3] net: lantiq_xrx200: increase napi poll weigth Aleksander Jan Bajkowski
2022-01-04 15:11 ` [PATCH net-next 3/3] net: lantiq_xrx200: convert to build_skb Aleksander Jan Bajkowski
2022-01-04 17:42 ` Eric Dumazet
2022-01-08 16:44 ` Aleksander Bajkowski
2022-01-06 1:30 ` [PATCH net-next 0/3] net: lantiq_xrx200: improve ethernet performance patchwork-bot+netdevbpf
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=20220104151144.181736-2-olek2@wp.pl \
--to=olek2@wp.pl \
--cc=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).