netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Louis Peens <louis.peens@corigine.com>
To: Mohammad Heib <mheib@redhat.com>
Cc: netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net] nfp: use irq_update_affinity_hint()
Date: Mon, 11 Nov 2024 07:33:12 +0200	[thread overview]
Message-ID: <ZzGXGEHCPUet3Jqw@LouisNoVo> (raw)
In-Reply-To: <20241107115002.413358-1-mheib@redhat.com>

On Thu, Nov 07, 2024 at 01:50:02PM +0200, Mohammad Heib wrote:
> irq_set_affinity_hint() is deprecated, Use irq_update_affinity_hint()
> instead. This removes the side-effect of actually applying the affinity.
> 
> The driver does not really need to worry about spreading its IRQs across
> CPUs. The core code already takes care of that. when the driver applies the
> affinities by itself, it breaks the users' expectations:
> 
> 1. The user configures irqbalance with IRQBALANCE_BANNED_CPULIST in
>    order to prevent IRQs from being moved to certain CPUs that run a
>    real-time workload.
> 
> 2. nfp device reopening will resets the affinity
>    in nfp_net_netdev_open().
> 
> 3. nfp has no idea about irqbalance's config, so it may move an IRQ to
>    a banned CPU. The real-time workload suffers unacceptable latency.
> 
> Signed-off-by: Mohammad Heib <mheib@redhat.com>
> ---
>  drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_common.c b/drivers/net/ethernet/netronome/nfp/nfp_net_common.c
> index 6e0929af0f72..98e098c09c03 100644
> --- a/drivers/net/ethernet/netronome/nfp/nfp_net_common.c
> +++ b/drivers/net/ethernet/netronome/nfp/nfp_net_common.c
> @@ -829,7 +829,7 @@ nfp_net_prepare_vector(struct nfp_net *nn, struct nfp_net_r_vector *r_vec,
>  		return err;
>  	}
>  
> -	irq_set_affinity_hint(r_vec->irq_vector, &r_vec->affinity_mask);
> +	irq_update_affinity_hint(r_vec->irq_vector, &r_vec->affinity_mask);
>  
>  	nn_dbg(nn, "RV%02d: irq=%03d/%03d\n", idx, r_vec->irq_vector,
>  	       r_vec->irq_entry);
> @@ -840,7 +840,7 @@ nfp_net_prepare_vector(struct nfp_net *nn, struct nfp_net_r_vector *r_vec,
>  static void
>  nfp_net_cleanup_vector(struct nfp_net *nn, struct nfp_net_r_vector *r_vec)
>  {
> -	irq_set_affinity_hint(r_vec->irq_vector, NULL);
> +	irq_update_affinity_hint(r_vec->irq_vector, NULL);
>  	nfp_net_napi_del(&nn->dp, r_vec);
>  	free_irq(r_vec->irq_vector, r_vec);
>  }
Looks good to me, thank you!

Reviewed-by: Louis Peens <louis.peens@corigine.com>
> -- 
> 2.34.3
> 

  parent reply	other threads:[~2024-11-11  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 11:50 [PATCH net] nfp: use irq_update_affinity_hint() Mohammad Heib
2024-11-10 13:31 ` Simon Horman
2024-11-11  5:33 ` Louis Peens [this message]
2024-11-12  0:10 ` 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=ZzGXGEHCPUet3Jqw@LouisNoVo \
    --to=louis.peens@corigine.com \
    --cc=mheib@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.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).