netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
	netdev@vger.kernel.org,  linux-kernel@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	 Frederic Weisbecker <frederic@kernel.org>,
	Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH] net/core/dev.c: enable timestamp static key if CPU isolation is configured
Date: Thu, 22 Feb 2024 10:34:17 +0100	[thread overview]
Message-ID: <2e3cf929a1aad9017cf57871c58675186f6d7939.camel@redhat.com> (raw)
In-Reply-To: <ZdSAWAwUxc5R46NH@tpad>

On Tue, 2024-02-20 at 07:35 -0300, Marcelo Tosatti wrote:
> For systems that use CPU isolation (via nohz_full), creating or destroying
> a socket with  timestamping (SOF_TIMESTAMPING_OPT_TX_SWHW) might 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>

This looks like net-next material, but it does not apply cleanly to the
net-next tree. Could you please rebase and repost including the 'net-
next' tag into the patch prefix?

Thanks!

Paolo


  reply	other threads:[~2024-02-22  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 10:35 [PATCH] net/core/dev.c: enable timestamp static key if CPU isolation is configured Marcelo Tosatti
2024-02-22  9:34 ` Paolo Abeni [this message]
2024-02-22 15:11 ` Willem de Bruijn
2024-02-22 17:52   ` Marcelo Tosatti
2024-02-22 18:42     ` Willem de Bruijn
     [not found] <Zc9493j46rZMRIDv@tpad>
2024-02-16 15:13 ` Eric Dumazet

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=2e3cf929a1aad9017cf57871c58675186f6d7939.camel@redhat.com \
    --to=pabeni@redhat.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=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;
as well as URLs for NNTP newsgroup(s).