From: Vladimir Oltean <olteanv@gmail.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
netdev <netdev@vger.kernel.org>,
erkin.bozoglu@xeront.com, "Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Felix Fietkau" <nbd@nbd.name>, "John Crispin" <john@phrozen.org>,
"Mark Lee" <Mark-MC.Lee@mediatek.com>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Landen Chao" <Landen.Chao@mediatek.com>,
"Sean Wang" <sean.wang@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>
Subject: Re: Choose a default DSA CPU port
Date: Fri, 24 Feb 2023 20:13:26 +0200 [thread overview]
Message-ID: <20230224181326.5lbph42bs566t2ci@skbuf> (raw)
In-Reply-To: <trinity-c58a37c3-aa55-48b3-9d6c-71520ad2a81d-1677262043715@3c-app-gmx-bap70>
On Fri, Feb 24, 2023 at 07:07:23PM +0100, Frank Wunderlich wrote:
> root@bpi-r2:~# ethtool -S eth0 | grep -v ': 0'
> NIC statistics:
> tx_bytes: 1643364546
> tx_packets: 1121377
> rx_bytes: 1270088499
> rx_packets: 1338400
> p06_TxUnicast: 1338274
> p06_TxMulticast: 120
> p06_TxBroadcast: 6
> p06_TxPktSz65To127: 525948
> p06_TxPktSz128To255: 5
> p06_TxPktSz256To511: 16
> p06_TxPktSz512To1023: 4
> p06_Tx1024ToMax: 812427
> p06_TxBytes: 1275442099
> p06_RxFiltering: 16
> p06_RxUnicast: 1121339
> p06_RxMulticast: 37
> p06_RxBroadcast: 1
> p06_RxPktSz64: 3
> p06_RxPktSz65To127: 43757
> p06_RxPktSz128To255: 3
> p06_RxPktSz256To511: 3
> p06_RxPktSz1024ToMax: 1077611
> p06_RxBytes: 1643364546
Looking at the drivers, I see pause frames aren't counted in ethtool -S,
so we wouldn't know this. However the slowdown *is* lossless, so the
hypothesis is still not disproved.
Could you please test after removing the "pause" property from the
switch's port@6 device tree node?
next prev parent reply other threads:[~2023-02-24 18:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 17:07 Choose a default DSA CPU port Arınç ÜNAL
2023-02-18 20:17 ` Frank Wunderlich
2023-02-18 20:17 ` Florian Fainelli
2023-02-18 20:52 ` Vladimir Oltean
2023-02-19 7:35 ` Arınç ÜNAL
2023-02-19 9:49 ` Aw: " Frank Wunderlich
2023-02-21 0:27 ` Vladimir Oltean
2023-02-22 17:17 ` Aw: " Frank Wunderlich
2023-02-22 18:06 ` Vladimir Oltean
2023-02-22 18:08 ` Arınç ÜNAL
2023-02-22 19:34 ` Vladimir Oltean
2023-02-22 19:42 ` Arınç ÜNAL
2023-02-24 18:07 ` Aw: " Frank Wunderlich
2023-02-24 18:13 ` Vladimir Oltean [this message]
2023-02-24 18:16 ` Vladimir Oltean
2023-02-24 18:31 ` Aw: " Frank Wunderlich
2023-02-22 19:39 ` Vladimir Oltean
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 20:44 Aw: " Frank Wunderlich
2023-02-24 21:08 ` Vladimir Oltean
2023-02-25 13:50 ` Aw: " Frank Wunderlich
2023-02-25 16:11 ` Arınç ÜNAL
2023-02-25 19:56 ` Arınç ÜNAL
2023-02-26 12:12 ` Aw: " Frank Wunderlich
2023-02-28 11:58 ` Vladimir Oltean
2023-02-28 13:48 ` Frank Wunderlich
2023-02-28 22:56 ` Vladimir Oltean
2023-03-01 6:38 ` Frank Wunderlich
2023-03-01 12:37 ` Vladimir Oltean
2023-03-06 18:20 ` Aw: " Frank Wunderlich
2023-03-07 17:43 ` Vladimir Oltean
2023-04-13 18:09 ` Aw: " Frank Wunderlich
2023-04-13 21:30 ` Frank Wunderlich
2023-05-16 19:29 ` Arınç ÜNAL
2023-05-17 16:10 ` Vladimir Oltean
2023-05-17 16:14 ` Arınç ÜNAL
2023-05-17 16:16 ` Vladimir Oltean
2023-05-18 10:36 ` Arınç ÜNAL
2023-05-18 14:24 ` Vladimir Oltean
2023-05-19 9:00 ` Arınç ÜNAL
2023-05-19 23:54 ` Vladimir Oltean
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=20230224181326.5lbph42bs566t2ci@skbuf \
--to=olteanv@gmail.com \
--cc=Landen.Chao@mediatek.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
/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).