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: <20220913140817.GA9091@hu-pkondeti-hyd.qualcomm.com>
Date:   Tue, 13 Sep 2022 19:38:17 +0530
From:   Pavan Kondeti <quic_pkondeti@...cinc.com>
To:     Johannes Weiner <hannes@...xchg.org>,
        Suren Baghdasaryan <surenb@...gle.com>,
        <linux-kernel@...r.kernel.org>
CC:     <quic_charante@...cinc.com>
Subject: PSI idle-shutoff

Hi

The fact that psi_avgs_work()->collect_percpu_times()->get_recent_times()
run from a kworker thread, PSI_NONIDLE condition would be observed as
there is a RUNNING task. So we would always end up re-arming the work.

If the work is re-armed from the psi_avgs_work() it self, the backing off
logic in psi_task_change() (will be moved to psi_task_switch soon) can't
help. The work is already scheduled. so we don't do anything there.

Probably I am missing some thing here. Can you please clarify how we
shut off re-arming the psi avg work?

Thanks,
Pavan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ