Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312367
| From | Frederic Weisbecker <fweisbec@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick |
| Date | 2016-01-19 17:30 +0100 |
| Message-ID | <qSHkm-1Ws-7@gated-at.bofh.it> (permalink) |
| References | <qQw9J-2at-33@gated-at.bofh.it> <qQw9J-2at-37@gated-at.bofh.it> <qSEcO-8kf-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jan 19, 2016 at 02:08:57PM +0100, Peter Zijlstra wrote: > On Wed, Jan 13, 2016 at 05:01:28PM +0100, Frederic Weisbecker wrote: > > The cpu load update on tick doesn't care about dynticks and as such is > > buggy when occuring on nohz ticks (including idle ticks) as it resets > > the jiffies snapshot that was recorded on nohz entry. We eventually > > ignore the potentially long tickless load that happened before the > > tick. > > I don't get it, how can we call scheduler_tick() while > tick_nohz_tick_stopped() ? tick_nohz_tick_stopped() (which is ts->tick_stopped == 1) doesn't actually mean that the tick is really stopped. It just means that the tick fires only when it's really needed (timer list expired, RCU stuff, irq_work, ...). So if you're lucky, the tick is really stopped because there is nothing that needs the tick in the future, otherwise (and it's probably most of the time) there is some tick that may well be programmed some time ahead in the future. So that's the kind of tick that can break the accounting of a whole long tickless load that just ran.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Peter Zijlstra <peterz@infradead.org> - 2016-01-19 14:10 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Frederic Weisbecker <fweisbec@gmail.com> - 2016-01-19 17:30 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Peter Zijlstra <peterz@infradead.org> - 2016-01-19 20:00 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Frederic Weisbecker <fweisbec@gmail.com> - 2016-01-19 23:40 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Byungchul Park <byungchul.park@lge.com> - 2016-01-20 06:50 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Byungchul Park <byungchul.park@lge.com> - 2016-01-20 11:30 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Thomas Gleixner <tglx@linutronix.de> - 2016-01-20 09:50 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Frederic Weisbecker <fweisbec@gmail.com> - 2016-01-20 18:40 +0100
Re: [PATCH 1/4] sched: Don't account tickless CPU load on tick Byungchul Park <byungchul.park@lge.com> - 2016-01-22 09:50 +0100
csiph-web