From: Paolo Abeni <pabeni@redhat.com>
To: Sergei Antonov <saproj@gmail.com>, netdev@vger.kernel.org
Cc: olteanv@gmail.com, andrew@lunn.ch, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net
Subject: Re: [PATCH v5 net-next] net: ftmac100: support mtu > 1500
Date: Thu, 27 Oct 2022 10:31:39 +0200 [thread overview]
Message-ID: <976d76cad07696c822acd44fbd534a614b7f85fc.camel@redhat.com> (raw)
In-Reply-To: <20221024175823.145894-1-saproj@gmail.com>
Hello,
On Mon, 2022-10-24 at 20:58 +0300, Sergei Antonov wrote:
> The ftmac100 controller considers packets >1518 (1500 + Ethernet + FCS)
> FTL (frame too long) and drops them. That is fine with mtu 1500 or less
> and it saves CPU time. When DSA is present, mtu is bigger (for VLAN
> tagging) and the controller's built-in behavior is not desired then. We
> can make the controller deliver FTL packets to the driver by setting
> FTMAC100_MACCR_RX_FTL. Then we have to check ftmac100_rxdes_frame_length()
> (packet length sans FCS) on packets marked with FTMAC100_RXDES0_FTL flag.
>
> Check for mtu > 1500 in .ndo_open() and set FTMAC100_MACCR_RX_FTL to let
> the driver FTL packets. Implement .ndo_change_mtu() and check for
> mtu > 1500 to set/clear FTMAC100_MACCR_RX_FTL dynamically.
>
> Fixes: 8d77c036b57c ("net: add Faraday FTMAC100 10/100 Ethernet driver")
For the records, Vladimir explicitly asked you to drop the 'Fixes' tag.
Such tag makes little sense for a net-next commit, especially when
referring to an old change - e.g. that did not enter mainline in this
release cycle.
Cheers,
Paolo
next prev parent reply other threads:[~2022-10-27 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:58 [PATCH v5 net-next] net: ftmac100: support mtu > 1500 Sergei Antonov
2022-10-27 8:31 ` Paolo Abeni [this message]
2022-10-27 11:35 ` Vladimir Oltean
2022-10-27 16:59 ` Sergei Antonov
2022-10-27 18:54 ` Vladimir Oltean
2022-10-28 15:21 ` Sergei Antonov
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=976d76cad07696c822acd44fbd534a614b7f85fc.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=saproj@gmail.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