Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tom Hromatka <tom.hromatka@oracle.com>,
tom.hromatka@oracle.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, fweisbec@gmail.com,
mingo@kernel.org, adobriyan@gmail.com
Subject: Re: [RESEND PATCH 2/2] /proc/stat: Simplify iowait and idle calculations when cpu is offline
Date: Sun, 13 Sep 2020 23:35:28 +0200 [thread overview]
Message-ID: <87d02ppdgf.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200909144122.77210-3-tom.hromatka@oracle.com>
On Wed, Sep 09 2020 at 08:41, Tom Hromatka wrote:
> A customer reported that when a cpu goes offline, the iowait and idle
> times reported in /proc/stat will sometimes spike. This is being
> caused by a different data source being used for these values when a
> cpu is offline.
>
> Prior to this patch:
>
> put the system under heavy load so that there is little idle time
>
> user nice system idle iowait
> cpu 109515 17 32111 220686 607
>
> take cpu1 offline
>
> user nice system idle iowait
> cpu 113742 17 32721 220724 612
>
> bring cpu1 back online
>
> user nice system idle iowait
> cpu 118332 17 33430 220687 607
>
> To prevent this, let's use the same data source whether a cpu is
> online or not.
Let's use? Your patch makes it use the same data source.
And again, neither the customer story nor the numbers are helpful to
understand the underlying problem. Also this lacks a reference to the
previous change which preserves the times accross a CPU offline/online
sequence.
> diff --git a/fs/proc/stat.c b/fs/proc/stat.c
> index 46b3293015fe..35b92539e711 100644
> --- a/fs/proc/stat.c
> +++ b/fs/proc/stat.c
> @@ -47,32 +47,20 @@ static u64 get_iowait_time(struct kernel_cpustat *kcs, int cpu)
>
> static u64 get_idle_time(struct kernel_cpustat *kcs, int cpu)
> {
> - u64 idle, idle_usecs = -1ULL;
> + u64 idle, idle_usecs;
>
> - if (cpu_online(cpu))
> - idle_usecs = get_cpu_idle_time_us(cpu, NULL);
> -
> - if (idle_usecs == -1ULL)
> - /* !NO_HZ or cpu offline so we can rely on cpustat.idle */
> - idle = kcs->cpustat[CPUTIME_IDLE];
> - else
> - idle = idle_usecs * NSEC_PER_USEC;
> + idle_usecs = get_cpu_idle_time_us(cpu, NULL);
> + idle = idle_usecs * NSEC_PER_USEC;
>
> return idle;
return get_cpu_idle_time_us(cpu, NULL) * NSEC_PER_USEC;
perhaps?
Thanks,
tglx
next prev parent reply other threads:[~2020-09-13 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:41 [RESEND PATCH 0/2] iowait and idle fixes in /proc/stat Tom Hromatka
2020-09-09 14:41 ` [RESEND PATCH 1/2] tick-sched: Do not clear the iowait and idle times Tom Hromatka
2020-09-13 21:27 ` Thomas Gleixner
2020-09-09 14:41 ` [RESEND PATCH 2/2] /proc/stat: Simplify iowait and idle calculations when cpu is offline Tom Hromatka
2020-09-10 12:14 ` Alexey Dobriyan
2020-09-13 21:35 ` Thomas Gleixner [this message]
2020-09-14 16:31 ` [RESEND PATCH 0/2] iowait and idle fixes in /proc/stat Tom Hromatka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d02ppdgf.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tom.hromatka@oracle.com \
--subject='Re: [RESEND PATCH 2/2] /proc/stat: Simplify iowait and idle calculations when cpu is offline' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).