* [PATCH net] netvsc: increase default receive buffer size
@ 2017-09-14 16:31 Stephen Hemminger
2017-09-14 17:02 ` David Miller
2017-09-15 21:48 ` David Miller
0 siblings, 2 replies; 4+ messages in thread
From: Stephen Hemminger @ 2017-09-14 16:31 UTC (permalink / raw)
To: kys, haiyangz, davem; +Cc: netdev, Stephen Hemminger, devel
The default receive buffer size was reduced by recent change
to a value which was appropriate for 10G and Windows Server 2016.
But the value is too small for full performance with 40G on Azure.
Increase the default back to maximum supported by host.
Fixes: 8b5327975ae1 ("netvsc: allow controlling send/recv buffer size")
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
---
drivers/net/hyperv/netvsc_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/net/hyperv/netvsc_drv.c
index c538a4f15f3b..d4902ee5f260 100644
--- a/drivers/net/hyperv/netvsc_drv.c
+++ b/drivers/net/hyperv/netvsc_drv.c
@@ -49,7 +49,7 @@
#define NETVSC_MIN_TX_SECTIONS 10
#define NETVSC_DEFAULT_TX 192 /* ~1M */
#define NETVSC_MIN_RX_SECTIONS 10 /* ~64K */
-#define NETVSC_DEFAULT_RX 2048 /* ~4M */
+#define NETVSC_DEFAULT_RX 10485 /* Max ~16M */
#define LINKCHANGE_INT (2 * HZ)
#define VF_TAKEOVER_INT (HZ / 10)
--
2.11.0
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH net] netvsc: increase default receive buffer size
2017-09-14 16:31 [PATCH net] netvsc: increase default receive buffer size Stephen Hemminger
@ 2017-09-14 17:02 ` David Miller
2017-09-14 17:49 ` Stephen Hemminger
2017-09-15 21:48 ` David Miller
1 sibling, 1 reply; 4+ messages in thread
From: David Miller @ 2017-09-14 17:02 UTC (permalink / raw)
To: stephen; +Cc: kys, haiyangz, netdev, devel, sthemmin
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 14 Sep 2017 09:31:07 -0700
> The default receive buffer size was reduced by recent change
> to a value which was appropriate for 10G and Windows Server 2016.
> But the value is too small for full performance with 40G on Azure.
> Increase the default back to maximum supported by host.
>
> Fixes: 8b5327975ae1 ("netvsc: allow controlling send/recv buffer size")
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
What other side effects are there to making this buffer so large?
Just curious...
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH net] netvsc: increase default receive buffer size
2017-09-14 17:02 ` David Miller
@ 2017-09-14 17:49 ` Stephen Hemminger
0 siblings, 0 replies; 4+ messages in thread
From: Stephen Hemminger @ 2017-09-14 17:49 UTC (permalink / raw)
To: David Miller; +Cc: netdev, haiyangz, sthemmin, devel
On Thu, 14 Sep 2017 10:02:03 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Thu, 14 Sep 2017 09:31:07 -0700
>
> > The default receive buffer size was reduced by recent change
> > to a value which was appropriate for 10G and Windows Server 2016.
> > But the value is too small for full performance with 40G on Azure.
> > Increase the default back to maximum supported by host.
> >
> > Fixes: 8b5327975ae1 ("netvsc: allow controlling send/recv buffer size")
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
>
> What other side effects are there to making this buffer so large?
>
> Just curious...
It increase latency and exercises bufferbloat avoidance on TCP.
The problem was the smaller buffer caused regressions in UDP
benchmarks on 40G Azure. One could argue that this is not a reasonable
benchmark but people run it. Apparently, Windows already went
the same thing and uses an even bigger buffer.
Longer term there will be more internal discussion with different
teams about what the receive latency and buffering needs to be.
Also, the issue goes away when doing accelerated networking (SR-IOV)
is more widely used.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH net] netvsc: increase default receive buffer size
2017-09-14 16:31 [PATCH net] netvsc: increase default receive buffer size Stephen Hemminger
2017-09-14 17:02 ` David Miller
@ 2017-09-15 21:48 ` David Miller
1 sibling, 0 replies; 4+ messages in thread
From: David Miller @ 2017-09-15 21:48 UTC (permalink / raw)
To: stephen; +Cc: netdev, haiyangz, sthemmin, devel
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 14 Sep 2017 09:31:07 -0700
> The default receive buffer size was reduced by recent change
> to a value which was appropriate for 10G and Windows Server 2016.
> But the value is too small for full performance with 40G on Azure.
> Increase the default back to maximum supported by host.
>
> Fixes: 8b5327975ae1 ("netvsc: allow controlling send/recv buffer size")
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Applied.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-09-15 21:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-14 16:31 [PATCH net] netvsc: increase default receive buffer size Stephen Hemminger
2017-09-14 17:02 ` David Miller
2017-09-14 17:49 ` Stephen Hemminger
2017-09-15 21:48 ` David Miller
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).