From: Nicolai Buchwitz <nb@tipi-net.de>
To: taozj888@163.com
Cc: theo.lebrun@bootlin.com, stable@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.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>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: macb: rate limit netdev error info print in the data path
Date: Fri, 02 Oct 2026 12:10:03 +0200 [thread overview]
Message-ID: <b06cb02d9b26ceff272d7e34927a7eac@tipi-net.de> (raw)
In-Reply-To: <20260930113520.392025-1-taozj888@163.com>
Hi Zijin
On 30.9.2026 13:35, taozj888@163.com wrote:
> From: taozijin <taozj888@163.com>
>
> Now the MACB ethernet driver print the netdev error information
> directly by netdev_err(), which would lead to a large number of
> error information print if there was a significant number of
> error or just jumbo packets exceeding the MTU received when booting.
> For example, it would print a large number of:
>
> macb PHYT0036:00 eth0: not whole frame pointed by descriptor
> macb PHYT0036:00 eth0: not whole frame pointed by descriptor
> ...
Out of interest: Is this a Phytium vendor kernel?
>
> in gem_rx() by received a large number of packets without
> RX_EOF flag set, especially with unknown packet
> type that would penetrate the hardware offload for the IP packets.
>
> The unlimited prints here would greatly bother and delay
> the system booting process unless the source stop sending
> packets since they occupy the console output bandwidth and
> other processes have to wait for the completion of printing those
> messages.
>
> So rate limit the netdev error information print in the receive
> and transmit data path.
>
> Fixes: 89e5785fc8a6 ("[PATCH] Atmel MACB ethernet driver")
IMHO the correct tag is 4df95131ea80 ("net/macb: change RX path for
GEM")?
At least the gem_rx() messages were introduced here.
> Cc: stable@vger.kernel.org
>
Drop the blank line as otherwise tooling might get confused and doesn't
get all tags correctly.
> Signed-off-by: Zijin Tao <taozj888@163.com>
> ---
> drivers/net/ethernet/cadence/macb_main.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/cadence/macb_main.c
> b/drivers/net/ethernet/cadence/macb_main.c
> index 8e5c034dc3a4..ca60960bec36 100644
> --- a/drivers/net/ethernet/cadence/macb_main.c
> +++ b/drivers/net/ethernet/cadence/macb_main.c
> @@ -1617,16 +1617,16 @@ static int gem_rx(struct macb_queue *queue,
> struct napi_struct *napi,
> count++;
>
> if (!(ctrl & MACB_BIT(RX_SOF) && ctrl & MACB_BIT(RX_EOF))) {
> - netdev_err(bp->netdev,
> - "not whole frame pointed by descriptor\n");
> + if (net_ratelimit())
> + netdev_err(bp->netdev, "not whole frame pointed by descriptor\n");
This will just hide the error message, but the split/drop is still
present.
How about limiting JML in macb_init_hw() properly?
if ((bp->caps & MACB_CAPS_JUMBO) && bp->jumbo_max_len) {
u32 jml = bp->rx_buffer_size - NET_IP_ALIGN +
ETH_FCS_LEN;
gem_writel(bp, JML, min(jml, bp->jumbo_max_len));
}
The code above is untested, so probably needs further tweaking. An
alternative could
be to handle the split frames in gem_rx() correctly.
> [...]
Thanks,
Nicolai
next prev parent reply other threads:[~2026-10-02 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:35 taozj888
2026-10-02 10:10 ` Nicolai Buchwitz [this message]
2026-10-02 12:08 ` Théo Lebrun
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=b06cb02d9b26ceff272d7e34927a7eac@tipi-net.de \
--to=nb@tipi-net.de \
--cc=andrew+netdev@lunn.ch \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hskinnemoen@atmel.com \
--cc=jeff@garzik.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=taozj888@163.com \
--cc=theo.lebrun@bootlin.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
all inboxes | Powered by JetHome®