From: Andrew Lunn <andrew@lunn.ch>
To: Shenwei Wang <shenwei.wang@nxp.com>
Cc: Wei Fang <wei.fang@nxp.com>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Clark Wang <xiaoning.wang@nxp.com>,
Stanislav Fomichev <sdf@fomichev.me>,
imx@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH v3 net-next 5/5] net: fec: enable the Jumbo frame support for i.MX8QM
Date: Sat, 23 Aug 2025 21:25:39 +0200 [thread overview]
Message-ID: <fd9af170-fb59-43fa-9eea-ff147f4a84a7@lunn.ch> (raw)
In-Reply-To: <20250823190110.1186960-6-shenwei.wang@nxp.com>
> @@ -1278,8 +1280,16 @@ fec_restart(struct net_device *ndev)
> if (fep->quirks & FEC_QUIRK_ENET_MAC) {
> /* enable ENET endian swap */
> ecntl |= FEC_ECR_BYTESWP;
> - /* enable ENET store and forward mode */
> - writel(FEC_TXWMRK_STRFWD, fep->hwp + FEC_X_WMRK);
> +
> + /* When Jumbo Frame is enabled, the FIFO may not be large enough
> + * to hold an entire frame. In this case, configure the interface
> + * to operate in cut-through mode, triggered by the FIFO threshold.
> + * Otherwise, enable the ENET store-and-forward mode.
> + */
> + if (fep->quirks & FEC_QUIRK_JUMBO_FRAME)
> + writel(0xF, fep->hwp + FEC_X_WMRK);
The quirk indicates the hardware is capable of jumbo frames, not that
jumbo frames are enabled. Don't you need to compare the mtu with
ETH_FRAME_LEN + ETH_FCS_LEN to say jumbo is enabled?
Is there a counter or other indication that the FIFO experienced an
underflow?
Andrew
next prev parent reply other threads:[~2025-08-23 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 19:01 [PATCH v3 net-next 0/5] net: fec: add the Jumbo frame support Shenwei Wang
2025-08-23 19:01 ` [PATCH v3 net-next 1/5] net: fec: use a member variable for maximum buffer size Shenwei Wang
2025-08-23 19:04 ` Andrew Lunn
2025-08-25 2:29 ` Wei Fang
2025-08-23 19:01 ` [PATCH v3 net-next 2/5] net: fec: add pagepool_order to support variable page size Shenwei Wang
2025-08-23 19:05 ` Andrew Lunn
2025-08-23 19:01 ` [PATCH v3 net-next 3/5] net: fec: add rx_frame_size to support configurable RX length Shenwei Wang
2025-08-23 19:11 ` Andrew Lunn
2025-08-23 20:09 ` Shenwei Wang
2025-08-23 20:54 ` Andrew Lunn
2025-08-23 21:18 ` Shenwei Wang
2025-08-24 16:13 ` Andrew Lunn
2025-08-25 2:46 ` Wei Fang
2025-08-25 18:57 ` Shenwei Wang
2025-08-23 19:01 ` [PATCH v3 net-next 4/5] net: fec: add change_mtu to support dynamic buffer allocation Shenwei Wang
2025-08-23 19:17 ` Andrew Lunn
2025-08-23 19:34 ` Shenwei Wang
2025-08-25 3:19 ` Wei Fang
2025-08-23 19:01 ` [PATCH v3 net-next 5/5] net: fec: enable the Jumbo frame support for i.MX8QM Shenwei Wang
2025-08-23 19:25 ` Andrew Lunn [this message]
2025-08-23 19:53 ` Shenwei Wang
2025-08-23 20:44 ` Andrew Lunn
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=fd9af170-fb59-43fa-9eea-ff147f4a84a7@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=imx@lists.linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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