From: Furong Xu <0x1207@gmail.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.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>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Vince Bridgers <vbridger@opensource.altera.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 1/3] net: stmmac: Limit the number of MTL queues to hardware capability
Date: Tue, 21 Jan 2025 14:25:20 +0800 [thread overview]
Message-ID: <20250121142520.0000702e@gmail.com> (raw)
In-Reply-To: <20250121044138.2883912-2-hayashi.kunihiko@socionext.com>
On Tue, 21 Jan 2025 13:41:36 +0900, Kunihiko Hayashi <hayashi.kunihiko@socionext.com> wrote:
> The number of MTL queues to use is specified by the parameter
> "snps,{tx,rx}-queues-to-use" from stmmac_platform layer.
>
> However, the maximum numbers of queues are constrained by upper limits
> determined by the capability of each hardware feature. It's appropriate
> to limit the values not to exceed the upper limit values and display
> a warning message.
>
> Fixes: d976a525c371 ("net: stmmac: multiple queues dt configuration")
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> index 7bf275f127c9..251a8c15637f 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> @@ -7232,6 +7232,19 @@ static int stmmac_hw_init(struct stmmac_priv *priv)
> if (priv->dma_cap.tsoen)
> dev_info(priv->device, "TSO supported\n");
>
> + if (priv->plat->rx_queues_to_use > priv->dma_cap.number_rx_queues) {
> + dev_warn(priv->device,
> + "Number of Rx queues exceeds dma capability (%d)\n",
> + priv->plat->rx_queues_to_use);
> + priv->plat->rx_queues_to_use = priv->dma_cap.number_rx_queues;
> + }
> + if (priv->plat->tx_queues_to_use > priv->dma_cap.number_tx_queues) {
> + dev_warn(priv->device,
> + "Number of Tx queues exceeds dma capability (%d)\n",
> + priv->plat->tx_queues_to_use);
I would prefer print these warnings like this:
dev_warn(priv->device, "Number of Tx queues (%u) exceeds dma capability (%u)\n",
priv->plat->tx_queues_to_use, priv->dma_cap.number_tx_queues);
And number_tx_queues, number_rx_queues are u32, so %u would be better.
This print format change is quite minor. Probably not worth a re-roll since one
can always view DMA capabilities by reading a debugfs entry.
next prev parent reply other threads:[~2025-01-21 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 4:41 [PATCH net v2 0/3] Limit devicetree parameters to hardware capability Kunihiko Hayashi
2025-01-21 4:41 ` [PATCH net v2 1/3] net: stmmac: Limit the number of MTL queues " Kunihiko Hayashi
2025-01-21 6:25 ` Furong Xu [this message]
2025-01-21 4:41 ` [PATCH net v2 2/3] net: stmmac: Limit FIFO size by " Kunihiko Hayashi
2025-01-21 17:14 ` Yanteng Si
2025-01-21 17:29 ` Russell King (Oracle)
2025-01-23 5:25 ` Kunihiko Hayashi
2025-01-22 4:07 ` Huacai Chen
2025-01-21 4:41 ` [PATCH net v2 3/3] net: stmmac: Specify hardware capability value when FIFO size isn't specified Kunihiko Hayashi
2025-01-21 10:25 ` [PATCH net v2 0/3] Limit devicetree parameters to hardware capability Russell King (Oracle)
2025-01-23 5:25 ` Kunihiko Hayashi
2025-01-23 16:31 ` Russell King (Oracle)
2025-01-24 4:19 ` Kunihiko Hayashi
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=20250121142520.0000702e@gmail.com \
--to=0x1207@gmail.com \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vbridger@opensource.altera.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).