From: Vladimir Oltean <olteanv@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Frank Wunderlich <frank-w@public-files.de>,
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: Wed, 22 Feb 2023 21:34:40 +0200 [thread overview]
Message-ID: <20230222193440.c2vzg7j7r32xwr5l@skbuf> (raw)
In-Reply-To: <9c9ab755-9b5e-4e76-0e3c-119d567fc39d@arinc9.com>
On Wed, Feb 22, 2023 at 09:08:03PM +0300, Arınç ÜNAL wrote:
> On 22.02.2023 21:06, Vladimir Oltean wrote:
> > On Wed, Feb 22, 2023 at 06:17:42PM +0100, Frank Wunderlich wrote:
> > > without Arincs Patch i got 940Mbit on gmac0, so something seems to affect the gmac when port5 is enabled.
> >
> > which patch?
>
> I believe Frank is referring to the patch series I submitted which adds
> port@5 to Bananapi BPI-R2. Without the patch, gmac0 is the default DSA
> master.
>
> https://lore.kernel.org/linux-mediatek/20230210182505.24597-1-arinc.unal@arinc9.com/
>
> Arınç
And with your patch + my patch, gmac0 is still the default DSA master,
but gmac1/port5 are also enabled. The claim is that switch port 6/gmac0
has lower bandwidth when switch port 5/gmac1 is enabled, than when it isn't?
Frank's testing is done on the MT7623 SoC (with the MT7530 switch),
an SoC which you have access to, since you've submitted those device
tree changes, correct? Do you confirm his result?
The posted ethtool stats are not sufficient to determine the cause of
the issue. It would be necessary to see all non-zero Ethernet counters
on both CPU port pairs:
ethtool -S eth0 | grep -v ': 0'
ethtool -S eth1 | grep -v ': 0'
to determine whether the cause of the performance degradation is packet
loss or just a lossless slowdown of some sorts. For example, the
degradation might be caused by the added flow control + uncalibrated
watermarks, not by the activation of the other GMAC.
next prev parent reply other threads:[~2023-02-22 19:34 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 [this message]
2023-02-22 19:42 ` Arınç ÜNAL
2023-02-24 18:07 ` Aw: " Frank Wunderlich
2023-02-24 18:13 ` Vladimir Oltean
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=20230222193440.c2vzg7j7r32xwr5l@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