From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
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>,
Yanteng Si <si.yanteng@linux.dev>, Furong Xu <0x1207@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 1/3] net: stmmac: Limit the number of MTL queues to hardware capability
Date: Mon, 27 Jan 2025 10:18:38 +0900 [thread overview]
Message-ID: <bc3734ba-e68d-4700-8596-2710f6101f8f@socionext.com> (raw)
In-Reply-To: <Z5N8-2XVAFBn1BCY@shell.armlinux.org.uk>
On 2025/01/24 20:43, Russell King (Oracle) wrote:
> On Fri, Jan 24, 2025 at 07:13:57PM +0900, Kunihiko Hayashi 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.
>>
>> This only works if the hardware capability has the upper limit values.
>>
>> 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 | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>> index 7bf275f127c9..be1e6fa6d557 100644
>> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>> @@ -7232,6 +7232,21 @@ static int stmmac_hw_init(struct stmmac_priv
> *priv)
>> if (priv->dma_cap.tsoen)
>> dev_info(priv->device, "TSO supported\n");
>>
>> + if (priv->dma_cap.number_rx_queues &&
>> + priv->dma_cap.number_rx_queues < priv->plat->rx_queues_to_use)
> {
>
> While this looks "nicer", which of these two do you think reads better
> and is easier to understand:
>
> "If priv->dma_cap.number_rx_queues is set, and
> priv->dma_cap.number_rx_queues is less than
> priv->plat->rx_queues_to_use then print a message about
> priv->plat->rx_queues_to_use exceeding priv->dma_cap.number_rx_queues"
>
> "If priv->dma_cap.number_rx_queues is set, and
> priv->plat->rx_queues_to_use is greater than
> priv->dma_cap.number_rx_queues, then print a message about
> priv->plat->rx_queues_to_use exceeding priv->dma_cap.number_rx_queues"
>
> With the former one has to mentally flip the test around in the if
> statement to check that it does indeed match the warning that is
> printed.
This patch focuses only on the conditional lines, however, certainly
it's not good to have the meaning of the message and the condition
reversed.
I'll fix it next.
Thank you,
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2025-01-27 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 10:13 [PATCH net v3 0/3] Limit devicetree parameters " Kunihiko Hayashi
2025-01-24 10:13 ` [PATCH net v3 1/3] net: stmmac: Limit the number of MTL queues " Kunihiko Hayashi
2025-01-24 11:43 ` Russell King (Oracle)
2025-01-27 1:18 ` Kunihiko Hayashi [this message]
2025-01-24 10:13 ` [PATCH net v3 2/3] net: stmmac: Limit FIFO size by " Kunihiko Hayashi
2025-01-24 10:13 ` [PATCH net v3 3/3] net: stmmac: Specify hardware capability value when FIFO size isn't specified 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=bc3734ba-e68d-4700-8596-2710f6101f8f@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=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=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=si.yanteng@linux.dev \
/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®