netdev - Re: [PATCH net-next -v6] net: enable timestamp static key if CPU isolation is configured

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 28 Mar 2024 14:05:04 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Marcelo Tosatti <mtosatti@...hat.com>, 
 netdev@...r.kernel.org
Cc: Willem de Bruijn <willemdebruijn.kernel@...il.com>, 
 Jakub Kicinski <kuba@...nel.org>, 
 Eric Dumazet <edumazet@...gle.com>, 
 Frederic Weisbecker <frederic@...nel.org>, 
 Valentin Schneider <vschneid@...hat.com>, 
 Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next -v6] net: enable timestamp static key if CPU
 isolation is configured

Marcelo Tosatti wrote:
> 
> For systems that use CPU isolation (via nohz_full), creating or destroying
> a socket with 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@...hat.com>

Reviewed-by: Willem de Bruijn <willemb@...gle.com>