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]
Message-ID: <YD4CdQqX5Lea1rB5@hirez.programming.kicks-ass.net>
Date:   Tue, 2 Mar 2021 10:16:37 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Feng Tang <feng.tang@...el.com>
Cc:     John Stultz <john.stultz@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Stephen Boyd <sboyd@...nel.org>, linux-kernel@...r.kernel.org,
        Qais Yousef <qais.yousef@....com>, andi.kleen@...el.com
Subject: Re: [PATCH] clocksource: don't run watchdog forever

On Tue, Mar 02, 2021 at 10:54:24AM +0800, Feng Tang wrote:
> clocksource watchdog runs every 500ms, which creates some OS noise.
> As the clocksource wreckage (especially for those that has per-cpu
> reading hook) usually happens shortly after CPU is brought up or
> after system resumes from sleep state, so add a time limit for
> clocksource watchdog to only run for a period of time, and make
> sure it run at least twice for each CPU.
> 
> Regarding performance data, there is no improvement data with the
> micro-benchmarks we have like hackbench/netperf/fio/will-it-scale
> etc. But it obviously reduces periodic timer interrupts, and may
> help in following cases:
> * When some CPUs are isolated to only run scientific or high
>   performance computing tasks on a NOHZ_FULL kernel, where there
>   is almost no interrupts, this could make it more quiet
> * On a cluster which runs a lot of systems in parallel with
>   barriers there are always enough systems which run the watchdog
>   and make everyone else wait
> 
> Signed-off-by: Feng Tang <feng.tang@...el.com>

Urgh.. so this hopes and prays that the TSC wrackage happens in the
first 10 minutes after boot.

Given the previous patch, the watchdog wouldn't be running at all on
modern machines, so why wreck it for the old machines where it's
actually needed?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ