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: <87r1qq7vqs.fsf@nanos.tec.linutronix.de>
Date:   Thu, 24 Sep 2020 22:41:47 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Tom Hromatka <tom.hromatka@...cle.com>, tom.hromatka@...cle.com,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        fweisbec@...il.com, mingo@...nel.org, adobriyan@...il.com
Subject: Re: [PATCH v2 1/2] tick-sched: Do not clear the iowait and idle times

On Tue, Sep 15 2020 at 13:36, Tom Hromatka wrote:
> Prior to this commit, the cpu idle and iowait data in /proc/stat were
> cleared when a CPU goes down.  When the CPU came back online, both idle
> and iowait times were restarted from 0.

Starting a commit message with 'Prior to this commit' is
pointless. Describe the factual problem which made you come up with this
change.

>
> This commit preserves the CPU's idle and iowait values when a CPU goes
> offline and comes back online.

'This commit does' is just a variation of 'This patch does'.

git grep 'This patch' Documentation/process/

Thanks,

        tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ