netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Jose Abreu <jose.abreu@synopsys.com>
Cc: Simon Huelck <simonmail@gmx.de>,
	Emiliano Ingrassia <ingrassia@epigenesys.com>,
	Gpeppe.cavallaro@st.com, alexandre.torgue@st.com,
	linux-amlogic@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: stmmac / meson8b-dwmac
Date: Sun, 17 Feb 2019 15:48:54 +0100	[thread overview]
Message-ID: <CAFBinCAJwk5Go4ZEt2cqVKyfeeOxsa-+3pfLpzQo=XNr5u4Shw@mail.gmail.com> (raw)
In-Reply-To: <330a523a-c1d6-4a99-3287-459096af0330@synopsys.com>

Hello Jose,

On Mon, Feb 11, 2019 at 2:45 PM Jose Abreu <jose.abreu@synopsys.com> wrote:
>
> Hello,
>
> On 2/9/2019 1:09 AM, Martin Blumenstingl wrote:
> > (it's interesting that the sending direction has 445 retries)
>
> I saw this before and I think it was related with COE. Can you
> please disable all offloading and try again?
OK, details are:

(before doing anything)
# ethtool -k eth0
Features for eth0:
rx-checksumming: on
tx-checksumming: on
       tx-checksum-ipv4: on
       tx-checksum-ip-generic: off [fixed]
       tx-checksum-ipv6: on
       tx-checksum-fcoe-crc: off [fixed]
       tx-checksum-sctp: off [fixed]
scatter-gather: on
       tx-scatter-gather: on
       tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
       tx-tcp-segmentation: off [fixed]
       tx-tcp-ecn-segmentation: off [fixed]
       tx-tcp-mangleid-segmentation: off [fixed]
       tx-tcp6-segmentation: off [fixed]
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]

this causes retries when running iperf3 in transmit mode.

with offloading disabled:

# ethtool -K eth0 rx off tx off
# ethtool -k eth0
Features for eth0:
rx-checksumming: off
tx-checksumming: off
       tx-checksum-ipv4: off
       tx-checksum-ip-generic: off [fixed]
       tx-checksum-ipv6: off
       tx-checksum-fcoe-crc: off [fixed]
       tx-checksum-sctp: off [fixed]
scatter-gather: on
       tx-scatter-gather: on
       tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
       tx-tcp-segmentation: off [fixed]
       tx-tcp-ecn-segmentation: off [fixed]
       tx-tcp-mangleid-segmentation: off [fixed]
       tx-tcp6-segmentation: off [fixed]
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[  5] local 192.168.1.131 port 58412 connected to 192.168.1.100 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   112 MBytes   937 Mbits/sec   32   59.4 KBytes
[  5]   1.00-2.00   sec   112 MBytes   937 Mbits/sec   25    290 KBytes
[  5]   2.00-3.00   sec   109 MBytes   915 Mbits/sec  150    279 KBytes
[  5]   3.00-4.00   sec   112 MBytes   941 Mbits/sec    0    334 KBytes
[  5]   4.00-5.00   sec   112 MBytes   941 Mbits/sec    0    342 KBytes
[  5]   5.00-6.00   sec   111 MBytes   934 Mbits/sec   98    320 KBytes
[  5]   6.00-7.00   sec   111 MBytes   929 Mbits/sec  123   76.4 KBytes
[  5]   7.00-8.00   sec   109 MBytes   917 Mbits/sec  119    277 KBytes
[  5]   8.00-9.00   sec   112 MBytes   941 Mbits/sec    0    314 KBytes
[  5]   9.00-10.00  sec   112 MBytes   940 Mbits/sec    0    318 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.09 GBytes   933 Mbits/sec  547             sender
[  5]   0.00-10.04  sec  1.09 GBytes   929 Mbits/sec                  receiver

iperf Done.

so for me disabling offloading didn't change anything.

Jose, is my command for disabling offloading correct?
Simon, does disabling offloading improve anything in your iperf2 or
real-world scenario on a kernel where you previously had performance
issues?


Regards
Martin

  parent reply	other threads:[~2019-02-17 14:49 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a38e643c-ed9f-c306-cc95-84f70ebc1f10@gmx.de>
     [not found] ` <CAFBinCDebPOsmrhSXecx48nGWHh7g_OGPbr1Y0M+n_v9Ht91ew@mail.gmail.com>
2019-01-17 21:23   ` stmmac / meson8b-dwmac Simon Huelck
2019-02-04 14:34     ` Martin Blumenstingl
2019-02-06 10:36       ` Emiliano Ingrassia
2019-02-06 18:04         ` Simon Huelck
2019-02-06 21:21         ` Simon Huelck
2019-02-07 19:30         ` Simon Huelck
2019-02-09  1:09           ` Martin Blumenstingl
2019-02-11 13:44             ` Jose Abreu
2019-02-14  7:21               ` Simon Huelck
2019-02-17 14:48               ` Martin Blumenstingl [this message]
2019-02-17 19:13                 ` Simon Huelck
2019-02-18  8:42                 ` Jose Abreu
2019-02-18  8:45                   ` Jose Abreu
2019-02-18 12:33                     ` Simon Huelck
2019-02-18 12:41                       ` Jose Abreu
2019-02-18 13:02                         ` Jose Abreu
2019-02-18 15:29                           ` Simon Huelck
2019-02-18 15:31                             ` Jose Abreu
2019-02-18 15:53                               ` Simon Huelck
2019-02-18 16:26                                 ` Jose Abreu
2019-02-18 16:40                                   ` Simon Huelck
2019-02-18 16:43                                     ` Jose Abreu
2019-02-18 16:51                                       ` Simon Huelck
2019-02-18 17:05                                         ` Jose Abreu
2019-02-18 18:05                                           ` Simon Huelck
2019-02-19  8:47                                             ` Jose Abreu
2019-02-19 19:41                                               ` Simon Huelck
2019-02-21 14:21                                                 ` Jerome Brunet
2019-02-21 17:27                                                   ` Simon Huelck
2019-02-21 17:46                                                     ` Jerome Brunet
2019-02-21 19:34                                                       ` Simon Huelck
2019-02-22 17:21                                                         ` Anand Moon
2019-02-24 15:00                                                       ` Simon Huelck
2019-02-24 15:02                                                         ` Simon Huelck
2019-02-24 19:42                                                         ` Sebastian Gottschall
2019-02-24 20:34                                                           ` Simon Huelck
2019-02-27 11:09                                                             ` Jose Abreu
2019-02-27 19:02                                                               ` Simon Huelck
2019-03-01  9:23                                                                 ` Jose Abreu
2019-03-05  9:55                                                                   ` Simon Huelck
2019-03-06 11:35                                                                     ` Simon Huelck
2019-03-06 11:45                                                                       ` Simon Huelck
2019-05-11 14:53                                                                   ` Simon Huelck
2019-05-13  9:07                                                                     ` Jose Abreu
2019-05-22 12:48                                                                       ` Simon Huelck
2019-05-22 14:02                                                                       ` Neil Armstrong
2019-02-27 21:03                                                               ` Simon Huelck
2019-02-18 17:05                                       ` Simon Huelck

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='CAFBinCAJwk5Go4ZEt2cqVKyfeeOxsa-+3pfLpzQo=XNr5u4Shw@mail.gmail.com' \
    --to=martin.blumenstingl@googlemail.com \
    --cc=Gpeppe.cavallaro@st.com \
    --cc=alexandre.torgue@st.com \
    --cc=ingrassia@epigenesys.com \
    --cc=jose.abreu@synopsys.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=simonmail@gmx.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).