From: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
To: Edward Cree <ecree.xilinx@gmail.com>,
netdev@vger.kernel.org, linux-net-drivers@amd.com
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, habetsm.xilinx@gmail.com
Subject: Re: [PATCH net-next] sfc: handle VI shortage on ef100 by readjusting the channels
Date: Tue, 30 May 2023 11:21:35 +0100 [thread overview]
Message-ID: <058f2e61-159f-536c-7a1b-eb58f742a66d@amd.com> (raw)
In-Reply-To: <40d9d9b9-0500-2c68-c047-20b1a090c0bf@gmail.com>
On 25/05/2023 15:51, Edward Cree wrote:
> On 24/05/2023 10:36, Pieter Jansen van Vuuren wrote:
>> When fewer VIs are allocated than what is allowed we can readjust
>> the channels by calling efx_mcdi_alloc_vis() again.
>>
>> Signed-off-by: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
>> Reviewed-by: Martin Habets <habetsm.xilinx@gmail.com>
>
> Reviewed-by: Edward Cree <ecree.xilinx@gmail.com>
> though see below for one nit (fix in a follow-up?)
>
>> ---
>> drivers/net/ethernet/sfc/ef100_netdev.c | 51 ++++++++++++++++++++++---
>> 1 file changed, 45 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/sfc/ef100_netdev.c b/drivers/net/ethernet/sfc/ef100_netdev.c
>> index d916877b5a9a..c201e001f3b8 100644
>> --- a/drivers/net/ethernet/sfc/ef100_netdev.c
>> +++ b/drivers/net/ethernet/sfc/ef100_netdev.c
>> @@ -40,19 +40,26 @@ static int ef100_alloc_vis(struct efx_nic *efx, unsigned int *allocated_vis)
>> unsigned int tx_vis = efx->n_tx_channels + efx->n_extra_tx_channels;
>> unsigned int rx_vis = efx->n_rx_channels;
>> unsigned int min_vis, max_vis;
>> + int rc;
>>
>> EFX_WARN_ON_PARANOID(efx->tx_queues_per_channel != 1);
>>
>> tx_vis += efx->n_xdp_channels * efx->xdp_tx_per_channel;
>>
>> max_vis = max(rx_vis, tx_vis);
>> - /* Currently don't handle resource starvation and only accept
>> - * our maximum needs and no less.
>> + /* We require at least a single complete TX channel worth of queues. */
>> + min_vis = efx->tx_queues_per_channel;
>> +
>> + rc = efx_mcdi_alloc_vis(efx, min_vis, max_vis,
>> + NULL, allocated_vis);
>
> I'd like a check here like
> if (rc == -EAGAIN)
> rc = -ESOMETHINGELSE;
> just to avoid confusion if the MC or MCDI machinery returns EAGAIN
> for whatever reason.
> Or perhaps better still, don't overload EAGAIN like this and instead
> have this function return 1 in the "we succeeded but didn't get
> max_vis" case (would need a comment above the function, documenting
> this), since that's not a value that can happen in-band.
>
> -ed
Thank you Ed. Yes, I will work with you on the follow-up and then avoid
overloading EAGAIN.
next prev parent reply other threads:[~2023-05-30 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:36 [PATCH net-next] sfc: handle VI shortage on ef100 by readjusting the channels Pieter Jansen van Vuuren
2023-05-24 10:09 ` Simon Horman
2023-05-24 13:52 ` Pieter Jansen van Vuuren
2023-05-24 14:25 ` Simon Horman
2023-05-25 14:51 ` Edward Cree
2023-05-30 10:21 ` Pieter Jansen van Vuuren [this message]
2023-05-26 9:20 ` patchwork-bot+netdevbpf
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=058f2e61-159f-536c-7a1b-eb58f742a66d@amd.com \
--to=pieter.jansen-van-vuuren@amd.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).