From: Greg Ungerer <gerg@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: sean.wang@mediatek.com, vivien.didelot@savoirfairelinux.com,
f.fainelli@gmail.com, netdev@vger.kernel.org, blogic@openwrt.org,
neil@brown.name
Subject: Re: [PATCH 0/3]: net: dsa: mt7530: support MT7530 in the MT7621 SoC
Date: Mon, 3 Dec 2018 16:47:01 +1000 [thread overview]
Message-ID: <06437893-2d15-a08e-8907-d246fb3e4a5b@kernel.org> (raw)
In-Reply-To: <20181130133313.GB11747@lunn.ch>
Hi Andrew,
On 30/11/18 11:33 pm, Andrew Lunn wrote:
>> 2. Maximal sized RX packets get silently dropped. So receive side packets
>> that are large (perfect case is the all-but-last packets in a fragemented
>> larger packet) appear to be dropped at the mt7621 ethernet MAC level.
>> The 7530 MIB switch register counters show receive packets at the physical
>> switch port side and at the CPU switch port - but I get no packets
>> received or errors in the 7621 ethernet MAC. If I set the mtu of the
>> server at the other end a little smaller (a few bytes is enough) then
>> I get all the packets through. It seems like the DSA/VLAN tag bytes
>> are causing a too large packet to get silently dropped somewhere.
>
> Hi Gerg
>
> Try increasing the MTU on the master device. Some hardware will reject
> receiving packets bigger than the MTU. But if you increase the MTU by
> the DSA header size, it will then receive the frame.
I tried increasing it on the master, and it fails to set:
# ifconfig eth0 mut 1500
# ifconfig eth0 mtu 1504
eth0: mtu greater than device maximum
SIOCSIFMTU: Invalid argument
Looking within that staging driver it seems to generously set the size
of the RX descriptor buffers, so there is enough room in them. And glancing
around the driver I don't see it using the MTU to restrict the receive
packaet size (though I may be missing it).
> I have a patchset i will be posting soon to do this automatically.
That would be good.
Regards
Greg
next prev parent reply other threads:[~2018-12-03 6:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:57 [PATCH 0/3]: net: dsa: mt7530: support MT7530 in the MT7621 SoC gerg
2018-11-30 7:57 ` [PATCH 1/3] net: dsa: mt7530: make clock/regulator setup optional gerg
2018-11-30 7:57 ` [PATCH 2/3] net: dsa: mt7530: optional setting CPU field in MFC register gerg
2018-11-30 7:57 ` [PATCH 3/3] dt-bindings: net: dsa: add new bindings MT7530 gerg
2018-11-30 17:41 ` Florian Fainelli
2018-12-03 7:03 ` Greg Ungerer
2018-12-03 13:19 ` Andrew Lunn
2018-11-30 11:27 ` [PATCH 0/3]: net: dsa: mt7530: support MT7530 in the MT7621 SoC René van Dorst
2018-11-30 13:25 ` Greg Ungerer
2018-11-30 11:30 ` René van Dorst
2018-11-30 12:16 ` Bjørn Mork
2018-11-30 13:41 ` Greg Ungerer
2018-11-30 13:42 ` Andrew Lunn
2018-12-03 7:20 ` Greg Ungerer
2018-12-03 11:34 ` Bjørn Mork
2018-12-03 14:00 ` René van Dorst
2018-12-03 14:02 ` John Crispin
2018-12-07 7:12 ` Greg Ungerer
2018-12-04 7:23 ` Greg Ungerer
2018-12-11 5:02 ` NeilBrown
2018-12-11 8:28 ` Bjørn Mork
2018-12-16 22:08 ` NeilBrown
2018-12-16 22:14 ` David Miller
2018-12-16 23:19 ` NeilBrown
2018-12-17 0:00 ` Florian Fainelli
2018-12-17 7:11 ` NeilBrown
2018-11-30 13:33 ` Andrew Lunn
2018-12-03 6:47 ` Greg Ungerer [this message]
2018-11-30 13:37 ` Andrew Lunn
2018-11-30 13:45 ` Greg Ungerer
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=06437893-2d15-a08e-8907-d246fb3e4a5b@kernel.org \
--to=gerg@kernel.org \
--cc=andrew@lunn.ch \
--cc=blogic@openwrt.org \
--cc=f.fainelli@gmail.com \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@savoirfairelinux.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).