public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Weilong Chen <chenweilong@huawei.com>
To: David Miller <davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
	<yoshfuji@linux-ipv6.org>, <sd@queasysnail.net>
Cc: Netdev <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<weiyongjun1@huawei.com>
Subject: Problem of TCP bandwidth drops when change MTU to a small value
Date: Tue, 15 Jan 2019 13:37:36 +0800	[thread overview]
Message-ID: <c5e705e9-fbfe-489d-c2b6-85eebf9f241f@huawei.com> (raw)

Hi, when we change the mtu to a small value, for example, ifconfig eth0 
mtu 68, IPERF test shows there's a great bandwidth drop while previous 
kernel versions don't.
Git bisect find the differences is from the patch 
28d35bcdd3925e7293408cdb8aa5f2aac5f0d6e3 (net: ipv4: don't let PMTU 
updates increase route MTU). After this patch, the stack send packets 
use a small mtu.

This problem can be reproduced easily on a qemu-kvm platform with virt 
nic E1000:
# ethtool -i eth0
driver: e1000
version: 7.3.21-k8-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:00:03.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
# # iperf -c 9.81.3.11 -t 3
------------------------------------------------------------
Client connecting to 9.81.3.11, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 9.83.1.202 port 44644 connected with 9.81.3.11 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 3.0 sec   336 MBytes   938 Mbits/sec
# ifconfig eth0 mtu 68
# iperf -c 9.81.3.11 -t 3
------------------------------------------------------------
Client connecting to 9.81.3.11, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 9.83.1.202 port 44646 connected with 9.81.3.11 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 3.3 sec  3.62 MBytes  9.18 Mbits/sec

             reply	other threads:[~2019-01-15  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15  5:37 Weilong Chen [this message]
2019-01-15  5:37 ` Problem of TCP bandwidth drops when change MTU to a small value Weilong Chen

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=c5e705e9-fbfe-489d-c2b6-85eebf9f241f@huawei.com \
    --to=chenweilong@huawei.com \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=weiyongjun1@huawei.com \
    --cc=yoshfuji@linux-ipv6.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