mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Artem S. Tashkinov" <t.artem@lycos.com>,
	pomac@vapor.com, linux-kernel@vger.kernel.org,
	tino.keitel@tikei.de, Len Brown <lenb@kernel.org>
Subject: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage
Date: Fri, 2 Dec 2011 11:39:21 +0100	[thread overview]
Message-ID: <20111202103921.GA29180@tiehlicka.suse.cz> (raw)
In-Reply-To: <20111201140749.GB4269@tiehlicka.suse.cz>

On Thu 01-12-11 15:07:49, Michal Hocko wrote:
[...]
> While implementation is not race free (we better not use locks in that
> path...) so we might race:
> 
> E.g.
> 
> CPU1			CPU2
> now = ktime_get
> 			tick_nohz_start_idle
> 				ts->idle_entrytime = now;
> if (ts->idle_active)
> 				ts->idle_active = 1
> [...]
> return idle_sleeptime
> 
> But this is OK because sleeptime will be more or less accurate. We just
> skip few ticks.
> 
> It would be worse if we had a race like:
> CPU1			CPU2
> now = ktime_get
> 			tick_nohz_start_idle
> 				now = ktime_get
> 				update_ts_time_stats()
> 				ts->idle_entrytime = now;
> 				ts->idle_active = 1
> if (ts->idle_active)
> 	delta = ktime_sub(now, idle_entrytime)
> 	ktime_add(idle_sleeptime, delta)
> 
> In this case we might get an overflow from ktime_sub but AFAIU the
> ktime_* magic the overflow should cause to get smaller idle_sleeptime
> in the end after ktime_add (we do not add a small number but rather
> subtract it), right?

Scratch that. Dunno why but I thought that ktime_t has unsigned values
but it is apparently not true (tv64 is s64). Anyway the above races should
be safe.

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

  reply	other threads:[~2011-12-02 10:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 22:28 pomac
2011-11-29  7:52 ` Michal Hocko
2011-11-29 11:38   ` Artem S. Tashkinov
2011-11-29 12:31     ` Michal Hocko
2011-11-29 12:44       ` Michal Hocko
2011-11-29 12:54         ` Artem S. Tashkinov
2011-11-29 13:10           ` Michal Hocko
2011-11-29 13:51             ` Artem S. Tashkinov
2011-11-29 22:51             ` Rafael J. Wysocki
2011-11-30 10:12               ` Michal Hocko
2011-11-30 19:56                 ` Rafael J. Wysocki
2011-12-01 14:07                   ` Michal Hocko
2011-12-02 10:39                     ` Michal Hocko [this message]
2011-12-02 13:35     ` Michal Hocko
2011-12-02 16:49       ` [PATCH] proc: Do not overflow get_{idle,iowait}_time for nohz (was: Re: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage) Michal Hocko
2011-12-02 17:59         ` Michal Hocko
2011-12-02 20:12           ` Artem S. Tashkinov
2011-12-05  8:56             ` Michal Hocko
2011-12-02 17:43       ` Re: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage Artem S. Tashkinov
2011-11-29 17:23   ` Ian Kumlien
2011-11-29 17:31   ` Ian Kumlien
2011-11-29 17:56     ` Michal Hocko
2011-11-29 18:37       ` Ian Kumlien

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=20111202103921.GA29180@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pomac@vapor.com \
    --cc=rjw@sisk.pl \
    --cc=t.artem@lycos.com \
    --cc=tino.keitel@tikei.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®