netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Habets <habetsm.xilinx@gmail.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>
Cc: ecree.xilinx@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, cmclachlan@solarflare.com,
	brouer@redhat.com, netdev@vger.kernel.org,
	Tianhao Zhao <tizhao@redhat.com>
Subject: Re: [PATCH net v2 2/2] sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels
Date: Wed, 1 Jun 2022 08:20:29 +0100	[thread overview]
Message-ID: <YpcTPexECg3LLrJb@gmail.com> (raw)
In-Reply-To: <20220601063603.15362-3-ihuguet@redhat.com>

On Wed, Jun 01, 2022 at 08:36:03AM +0200, Íñigo Huguet wrote:
> tx_channel_offset is calculated in efx_allocate_msix_channels, but it is
> also calculated again in efx_set_channels because it was originally done
> there, and when efx_allocate_msix_channels was introduced it was
> forgotten to be removed from efx_set_channels.
> 
> Moreover, the old calculation is wrong when using
> efx_separate_tx_channels because now we can have XDP channels after the
> TX channels, so n_channels - n_tx_channels doesn't point to the first TX
> channel.
> 
> Remove the old calculation from efx_set_channels, and add the
> initialization of this variable if MSI or legacy interrupts are used,
> next to the initialization of the rest of the related variables, where
> it was missing.
> 
> This has been already done for sfc, do it also for sfc_siena.
> 
> Fixes: 3990a8fffbda ("sfc: allocate channels for XDP tx queues")
> Reported-by: Tianhao Zhao <tizhao@redhat.com>
> Signed-off-by: Íñigo Huguet <ihuguet@redhat.com>

Acked-by: Martin Habets <habetsm.xilinx@gmail.com>

> ---
>  drivers/net/ethernet/sfc/siena/efx_channels.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/ethernet/sfc/siena/efx_channels.c b/drivers/net/ethernet/sfc/siena/efx_channels.c
> index 2465cf4d505c..017212a40df3 100644
> --- a/drivers/net/ethernet/sfc/siena/efx_channels.c
> +++ b/drivers/net/ethernet/sfc/siena/efx_channels.c
> @@ -299,6 +299,7 @@ int efx_siena_probe_interrupts(struct efx_nic *efx)
>  		efx->n_channels = 1;
>  		efx->n_rx_channels = 1;
>  		efx->n_tx_channels = 1;
> +		efx->tx_channel_offset = 0;
>  		efx->n_xdp_channels = 0;
>  		efx->xdp_channel_offset = efx->n_channels;
>  		rc = pci_enable_msi(efx->pci_dev);
> @@ -319,6 +320,7 @@ int efx_siena_probe_interrupts(struct efx_nic *efx)
>  		efx->n_channels = 1 + (efx_siena_separate_tx_channels ? 1 : 0);
>  		efx->n_rx_channels = 1;
>  		efx->n_tx_channels = 1;
> +		efx->tx_channel_offset = 1;
>  		efx->n_xdp_channels = 0;
>  		efx->xdp_channel_offset = efx->n_channels;
>  		efx->legacy_irq = efx->pci_dev->irq;
> @@ -958,10 +960,6 @@ int efx_siena_set_channels(struct efx_nic *efx)
>  	struct efx_channel *channel;
>  	int rc;
>  
> -	efx->tx_channel_offset =
> -		efx_siena_separate_tx_channels ?
> -		efx->n_channels - efx->n_tx_channels : 0;
> -
>  	if (efx->xdp_tx_queue_count) {
>  		EFX_WARN_ON_PARANOID(efx->xdp_tx_queues);
>  
> -- 
> 2.34.1

  reply	other threads:[~2022-06-01  7:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 13:40 [PATCH net 0/2] sfc/siena: fix some efx_separate_tx_channels errors Íñigo Huguet
2022-05-31 13:40 ` [PATCH net 1/2] sfc/siena: fix considering that all channels have TX queues Íñigo Huguet
2022-05-31 13:40 ` [PATCH net 2/2] sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels Íñigo Huguet
2022-05-31 15:37 ` [PATCH net 0/2] sfc/siena: fix some efx_separate_tx_channels errors Jakub Kicinski
2022-06-01  6:23   ` Íñigo Huguet
2022-06-01  6:36 ` [PATCH net v2 " Íñigo Huguet
2022-06-01  6:36   ` [PATCH net v2 1/2] sfc/siena: fix considering that all channels have TX queues Íñigo Huguet
2022-06-01  6:36   ` [PATCH net v2 2/2] sfc/siena: fix wrong tx channel offset with efx_separate_tx_channels Íñigo Huguet
2022-06-01  7:20     ` Martin Habets [this message]
2022-06-02  1:00   ` [PATCH net v2 0/2] sfc/siena: fix some efx_separate_tx_channels errors 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=YpcTPexECg3LLrJb@gmail.com \
    --to=habetsm.xilinx@gmail.com \
    --cc=brouer@redhat.com \
    --cc=cmclachlan@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=ihuguet@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tizhao@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).