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-next>] [day] [month] [year] [list]
Message-ID: <4511619.LvFx2qVVIh@kreacher>
Date:   Tue, 01 Aug 2023 21:35:15 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Linux PM <linux-pm@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Anna-Maria Behnsen <anna-maria@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Frederic Weisbecker <frederic@...nel.org>,
        Kajetan Puchalski <kajetan.puchalski@....com>
Subject: [RFC/RFT][PATCH v1 0/2] cpuidle: teo: Do not check timers unconditionally every time

Hi Folks,

This is on top of the fixes series posted previously:

https://lore.kernel.org/linux-pm/4515817.LvFx2qVVIh@kreacher/

(I'll put it all into one git branch tomorrow).

I started to play with the idea described here

https://lore.kernel.org/linux-pm/CAJZ5v0hQh2Pg_uXxj8KBRw3oLS1WdsU+rUafBAAq7dRdbRwYSA@mail.gmail.com/

and this is the result.

Note that this is completely experimental, even though it doesn't kill any of
the test boxes I've run it on.

Patch [1/2] moves the tick_nohz_get_sleep_length() call in teo_select() after
a preliminary idle state selection based on statistics and patch [2/2] adds
checks to avoid it completely if the idle state selected so far is shallow
enough.

I would appreciate checking if this actually makes any difference.

Thanks!



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ