From: Jakub Kicinski <kuba@kernel.org>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
loongarch@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Chong Qiao <qiaochong@loongson.cn>
Subject: Re: [PATCH] net: stmmac: dwmac-loongson: Set correct {tx,rx}_fifo_size
Date: Mon, 27 Jan 2025 14:06:07 -0800 [thread overview]
Message-ID: <20250127140607.6b3617df@kernel.org> (raw)
In-Reply-To: <20250121093703.2660482-1-chenhuacai@loongson.cn>
On Tue, 21 Jan 2025 17:37:03 +0800 Huacai Chen wrote:
> Now for dwmac-loongson {tx,rx}_fifo_size are uninitialised, which means
> zero. This means dwmac-loongson doesn't support changing MTU,
Please provide more details here than "doesn't support changing".
Does it return an error every time, but the device is operating
correctly?
Do the flow control thresholds also get programmed incorrectly?
> so set the
> correct tx_fifo_size and rx_fifo_size for it (16KB multiplied by channel
> counts).
>
> Note: the Fixes tag is not exactly right, but it is a key commit of the
> dwmac-loongson series.
Please pick a better one, then. Oldest commit where issue can be
observed by the user is usually a safe choice.
Please use 12 chars of the hash in the tag.
> + plat->tx_fifo_size = SZ_16K * plat->tx_queues_to_use;
> + plat->rx_fifo_size = SZ_16K * plat->rx_queues_to_use;
Is this really right? 16k times the number of queues seems like you're
just trying to get the main driver to calculate 16k.
What if user decreases the queue count? Maybe you should add a way to
communicate the fifo size regardless of the queue count to the main
driver?
--
pw-bot: cr
next prev parent reply other threads:[~2025-01-27 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 9:37 [PATCH] net: stmmac: dwmac-loongson: Set correct {tx,rx}_fifo_size Huacai Chen
2025-01-22 13:34 ` Simon Horman
2025-01-24 9:09 ` Huacai Chen
2025-01-22 14:49 ` Yanteng Si
2025-01-27 22:06 ` Jakub Kicinski [this message]
2025-02-06 7:52 ` Huacai Chen
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=20250127140607.6b3617df@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiaochong@loongson.cn \
--cc=stable@vger.kernel.org \
/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).