From: Simon Horman <horms@kernel.org>
To: Joe Damato <jdamato@fastly.com>,
Stanislav Fomichev <sdf@fomichev.me>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jiri Pirko <jiri@resnulli.us>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC net-next 1/6] netdevice: Add napi_affinity_no_change
Date: Tue, 13 Aug 2024 14:05:56 +0100 [thread overview]
Message-ID: <20240813130556.GD5183@kernel.org> (raw)
In-Reply-To: <ZrsjLS8wRcYL3HxQ@LQ3V64L9R2.home>
On Tue, Aug 13, 2024 at 10:11:09AM +0100, Joe Damato wrote:
> On Mon, Aug 12, 2024 at 03:36:42PM -0700, Stanislav Fomichev wrote:
> > On 08/12, Joe Damato wrote:
> > > On Mon, Aug 12, 2024 at 01:23:27PM -0700, Stanislav Fomichev wrote:
> > > > On 08/12, Joe Damato wrote:
> > > > > Several drivers have their own, very similar, implementations of
> > > > > determining if IRQ affinity has changed. Create napi_affinity_no_change
> > > > > to centralize this logic in the core.
> > > > >
> > > > > This will be used in following commits for various drivers to eliminate
> > > > > duplicated code.
> > > > >
>
> [...]
>
> > > > > +bool napi_affinity_no_change(unsigned int irq)
> > > > > +{
> > > > > + int cpu_curr = smp_processor_id();
> > > > > + const struct cpumask *aff_mask;
> > > > > +
> > > >
> > > > [..]
> > > >
> > > > > + aff_mask = irq_get_effective_affinity_mask(irq);
> > > >
> > > > Most drivers don't seem to call this on every napi_poll (and
> > > > cache the aff_mask somewhere instead). Should we try to keep this
> > > > out of the past path as well?
> > >
> > > Hm, I see what you mean. It looks like only gve calls it on every
> > > poll, while the others use a cached value.
> > >
> > > Maybe a better solution is to:
> > > 1. Have the helper take the cached affinity mask from the driver
> > > and return true/false.
> > > 2. Update gve to cache the mask (like the other 4 are doing).
> >
> > SG! GVE is definitely the outlier here.
>
> OK, I'll hack on that for rfcv2 and see what it looks like. Thanks
> for the suggestion.
>
> Hopefully the maintainers (or other folks) will chime in on whether
> or not I should submit fixes for patches 4 - 6 for the type mismatch
> stuff first or just handle it all together.
<2c>
Patches 4 - 6 seem more like clean-ups that fixes to me: they aren't fixing
any bugs are they? So I would just keep them as part of this patchset
unless it becomes unwieldy.
</2c>
In any case thanks for all your good work in this area.
next prev parent reply other threads:[~2024-08-13 13:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 14:56 [Intel-wired-lan] [RFC net-next 0/6] Cleanup IRQ affinity checks in several drivers Joe Damato
2024-08-12 14:56 ` Joe Damato
2024-08-12 14:56 ` [RFC net-next 1/6] netdevice: Add napi_affinity_no_change Joe Damato
2024-08-12 20:23 ` Stanislav Fomichev
2024-08-12 21:08 ` Joe Damato
2024-08-12 22:36 ` Stanislav Fomichev
2024-08-13 9:11 ` Joe Damato
2024-08-13 10:03 ` Joe Damato
2024-08-13 13:05 ` Simon Horman [this message]
2024-08-12 14:56 ` [RFC net-next 2/6] mlx5: Use napi_affinity_no_change Joe Damato
2024-08-12 14:56 ` [RFC net-next 3/6] gve: " Joe Damato
2024-08-13 18:55 ` Shailend Chand
2024-08-13 21:44 ` Joe Damato
2024-08-13 21:50 ` Shailend Chand
2024-08-12 14:56 ` [Intel-wired-lan] [RFC net-next 4/6] i40e: " Joe Damato
2024-08-12 14:56 ` Joe Damato
2024-08-12 14:56 ` [Intel-wired-lan] [RFC net-next 5/6] iavf: " Joe Damato
2024-08-12 14:56 ` Joe Damato
2024-08-12 14:56 ` [RFC net-next 6/6] mlx4: " Joe Damato
2024-08-14 0:17 ` [Intel-wired-lan] [RFC net-next 0/6] Cleanup IRQ affinity checks in several drivers Jakub Kicinski
2024-08-14 0:17 ` Jakub Kicinski
2024-08-14 7:14 ` [Intel-wired-lan] " Joe Damato
2024-08-14 7:14 ` Joe Damato
2024-08-14 12:12 ` [Intel-wired-lan] " Joe Damato
2024-08-14 12:12 ` Joe Damato
2024-08-14 15:09 ` [Intel-wired-lan] " Jakub Kicinski
2024-08-14 15:09 ` Jakub Kicinski
2024-08-14 15:19 ` [Intel-wired-lan] " Joe Damato
2024-08-14 15:19 ` Joe Damato
2024-08-14 16:03 ` [Intel-wired-lan] " Shay Drori
2024-08-14 16:03 ` Shay Drori
2024-08-14 18:01 ` [Intel-wired-lan] " Joe Damato
2024-08-14 18:01 ` Joe Damato
2024-08-15 0:20 ` [Intel-wired-lan] " Jakub Kicinski
2024-08-15 0:20 ` Jakub Kicinski
2024-08-15 10:22 ` [Intel-wired-lan] " Joe Damato
2024-08-15 10:22 ` Joe Damato
2024-08-20 6:40 ` [Intel-wired-lan] " Shay Drori
2024-08-20 6:40 ` Shay Drori
2024-08-20 8:33 ` [Intel-wired-lan] " Joe Damato
2024-08-20 8:33 ` Joe Damato
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=20240813130556.GD5183@kernel.org \
--to=horms@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.