From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [RFC][PATCH 0/3] sched: skip_clock_update madness
Date: Mon, 5 Jan 2015 12:50:54 +0100 [thread overview]
Message-ID: <20150105115054.GE3337@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1420454949.5266.138.camel@marge.simpson.net>
On Mon, Jan 05, 2015 at 11:49:09AM +0100, Mike Galbraith wrote:
> On Mon, 2015-01-05 at 11:18 +0100, Peter Zijlstra wrote:
> > Hi,
> >
> > So the big lockup thread got me looking at the skip_clock_update stuff again
> > and here's what I came up with.
> >
> > It seems to build a kernel without generating lockdep splats.
> >
> > Mike can you see if it cures the wobblies you were seeing?
>
> Nope, those hiccups were production IO beasts from hell staying in the
> kernel for ages at a time. Watchdog being falsely credited with what is
> usually dinky wakeup -> switch delta throttled it effectively forever.
OK, It's Monday and I'm still trying to bootstrap my post xmas brain. Is
that: Nope - can't check, or: Nope - doesn't fix wobblies ?
next prev parent reply other threads:[~2015-01-05 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 10:18 [RFC][PATCH 0/3] sched: skip_clock_update madness Peter Zijlstra
2015-01-05 10:18 ` [RFC][PATCH 1/3] sched: Validate rq_clock*() serialization Peter Zijlstra
2015-01-14 14:03 ` [tip:sched/core] sched/core: " tip-bot for Peter Zijlstra
2015-05-30 1:03 ` Sasha Levin
2015-06-04 2:28 ` Wanpeng Li
2015-01-05 10:18 ` [RFC][PATCH 2/3] sched: Rework rq->clock update skips Peter Zijlstra
2015-01-14 14:03 ` [tip:sched/core] sched/core: " tip-bot for Peter Zijlstra
2015-01-05 10:18 ` [RFC][PATCH 3/3] sched,debug: Print clock_task Peter Zijlstra
2015-01-14 14:03 ` [tip:sched/core] sched/debug: Print rq->clock_task tip-bot for Peter Zijlstra
2015-01-05 10:49 ` [RFC][PATCH 0/3] sched: skip_clock_update madness Mike Galbraith
2015-01-05 11:50 ` Peter Zijlstra [this message]
2015-01-05 12:07 ` Mike Galbraith
2015-01-05 13:59 ` Peter Zijlstra
2015-01-06 5:55 ` Mike Galbraith
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=20150105115054.GE3337@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.com \
/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