From: Denys Vlasenko <dvlasenk@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Fernando Luis Vazquez Cao <fernando_b1@lab.ntt.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH 2/3] nohz: Synchronize sleep time stats with memory barriers
Date: Thu, 24 Apr 2014 20:36:03 +0200 [thread overview]
Message-ID: <53595993.2080905@redhat.com> (raw)
In-Reply-To: <20140424001640.GA27571@localhost.localdomain>
On 04/24/2014 02:16 AM, Frederic Weisbecker wrote:
>> + again:
>> + active = ACCESS_ONCE(ts->idle_active);
>> + smp_rmb();
>> + count = ACCESS_ONCE(ts->idle_sleeptime);
>> + if (active == 1) {
>> + ktime_t delta, start;
>> +
>> + smp_rmb();
>> + start = ACCESS_ONCE(ts->idle_entrytime);
>> + if (start.tv64 == 0) {
>> + /*
>> + * Other CPU is updating the count.
>> + * We don't know whether fetched count is valid.
>> + */
>> + goto again;
>> + }
>> + delta = ktime_sub(now, start);
>> + count = ktime_add(count, delta);
>
> There is still a possibility that you race with an updater here.
> Lets take these initial values, all of which belong to ts(CPU 1):
>
> // idle_sleeptime == 0
> // idle_entrytime == 0
> // ktime_get() == 100
> // idle_active = 1
>
> CPU 0 CPU 1
>
> count = idle_sleeptime // = 0
> tick_nohz_stop_idle();
> tick_nohz_start_idle();
> /* now idle_sleeptime == 100
> and idle_entrytime == 100
> ktime_get() is still 100
> and idle_active is still 1
> as it has toggled two times */
> delta = now - idle_entrytime; // 100 - 100
> count += delta // == 0
>
> Then you get the spurious 0 result.
>
> So memory barriers probably aren't enough here. seqcount would solve the issue as it maintains
> update seq tokens.
I think you are right. I'll use your approach (seqcount) in the next version.
next prev parent reply other threads:[~2014-04-24 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 19:00 [PATCH 1/3] nohz: Only update sleeptime stats locally Denys Vlasenko
2014-04-23 19:00 ` [PATCH 2/3] nohz: Synchronize sleep time stats with memory barriers Denys Vlasenko
2014-04-24 0:16 ` Frederic Weisbecker
2014-04-24 18:36 ` Denys Vlasenko [this message]
2014-04-23 19:00 ` [PATCH 3/3] nohz: Fix iowait overcounting if iowait task migrates Denys Vlasenko
2014-04-24 0:37 ` Frederic Weisbecker
2014-04-24 7:07 ` Peter Zijlstra
2014-04-24 18:38 ` Denys Vlasenko
2014-04-24 8:19 ` Hidetoshi Seto
2014-04-24 18:43 ` Denys Vlasenko
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=53595993.2080905@redhat.com \
--to=dvlasenk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.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
Powered by JetHome