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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6dc758b-492d-1000-24e5-643e38d3166e@huawei.com>
Date:   Mon, 14 Feb 2022 17:40:55 +0800
From:   Yu Liao <liaoyu15@...wei.com>
To:     <frederic@...nel.org>
CC:     <paulmck@...nel.org>, <linux-kernel@...r.kernel.org>,
        <liwei391@...wei.com>
Subject: Re: Question about nohz and sysidle

Sorry, I sent to the old email address.

On 2022/2/14 16:28, Yu Liao wrote:
> Hi Frederic,
> 
> I'm working on an issue about nohz. When NO_HZ_FULL is enabled, CPU 0 
> handles the timekeeping duty on behalf of all other CPUs, which means 
> CPU 0 never stop tick even in sysidle state. This is a powersaving issue.
> 
> I found your patchset (nohz: Support sysidle) in the below link.
> https://lore.kernel.org/all/1406569056-30217-1-git-send-email-fweisbec@gmail.com/ 
> 
> But these patches haven't been merged into mainline yet and sysidle 
> state detection has been removed by commit fe5ac724d81a (rcu: Remove 
> nohz_full full-system-idle state machine) as well.
> 
> I tried your patches and it does work, why are we no longer 
> working on stopping timekeeping duty when all full dynticks CPUs are idle?
> 
> Thanks,
> Yu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ