From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Frederic Weisbecker <frederic@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next -v3] net/core/dev.c: enable timestamp static key if CPU isolation is configured
Date: Thu, 07 Mar 2024 04:07:17 -0500 [thread overview]
Message-ID: <65e983c5155fa_f5b792941b@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <65e82e533857c_a463929462@willemb.c.googlers.com.notmuch>
Willem de Bruijn wrote:
> Marcelo Tosatti wrote:
> >
> > For systems that use CPU isolation (via nohz_full), creating or destroying
> > a socket with
>
> - timestamping (SOCK_TIMESTAMPING_RX_SOFTWARE) might cause a
> + SO_TIMESTAMP, SO_TIMESTAMPNS or SO_TIMESTAMPING with flag
> + SOF_TIMESTAMPING_RX_SOFTWARE will cause a
>
> > static key to be enabled/disabled. This in turn causes undesired
> > IPIs to isolated CPUs.
> >
> > So enable the static key unconditionally, if CPU isolation is enabled,
> > thus avoiding the IPIs.
> >
> > Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
> > diff --git a/net/core/dev.c b/net/core/dev.c
> > index c588808be77f..15a32f5900e6 100644
> > --- a/net/core/dev.c
> > +++ b/net/core/dev.c
> > @@ -155,6 +155,7 @@
> > #include <net/netdev_rx_queue.h>
> > #include <net/page_pool/types.h>
> > #include <net/page_pool/helpers.h>
> > +#include <linux/sched/isolation.h>
> >
> > #include "dev.h"
> > #include "net-sysfs.h"
> > @@ -11851,3 +11852,14 @@ static int __init net_dev_init(void)
> > }
> >
> > subsys_initcall(net_dev_init);
> > +
> > +static int __init net_dev_late_init(void)
> > +{
> > + /* avoid static key IPIs to isolated CPUs */
> > + if (housekeeping_enabled(HK_TYPE_MISC))
> > + net_enable_timestamp();
> > +
> > + return 0;
> > +}
> > +
> > +late_initcall(net_dev_late_init);
> >
>
> Can this be included in the existing net_dev_init
> subsys_initcall?
You sent a v4, but can you answer this question?
prev parent reply other threads:[~2024-03-07 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:46 [PATCH net-next -v3] net/core/dev.c: enable timestamp static key if CPU isolation is configured Marcelo Tosatti
2024-03-06 8:50 ` Willem de Bruijn
2024-03-07 9:07 ` Willem de Bruijn [this message]
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=65e983c5155fa_f5b792941b@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vschneid@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