From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Kevin Hilman" <khilman@linaro.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Amit Kucheria" <amit.kucheria@linaro.org>,
"Lists linaro-kernel" <linaro-kernel@lists.linaro.org>,
"Linaro Networking" <linaro-networking@linaro.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?
Date: Wed, 15 Jan 2014 12:34:06 +0100 [thread overview]
Message-ID: <20140115113406.GC31570@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKohpomtNWZTn4zhf3og=Ff8LvBMH_68tLNgYLOyBK5Az6WXuA@mail.gmail.com>
On Wed, Jan 15, 2014 at 04:17:26PM +0530, Viresh Kumar wrote:
> On 15 January 2014 16:08, Peter Zijlstra <peterz@infradead.org> wrote:
> > Nah, its just ugly and we should fix it. You need to be careful to not
> > place tasks in a cpuset you're going to unplug though, that'll give
> > funny results.
>
> Okay. So how do you suggest to get rid of cases like a work queued
> on CPU1 initially and because it gets queued again from its work handler,
> it stays on the same CPU forever.
We should have a cpuset.quiesce control or something that moves all
timers out.
> And then there were timer overflow events that occur because hrtimer
> is started by tick-sched stuff for 450 seconds later in time.
-ENOPARSE
next prev parent reply other threads:[~2014-01-15 11:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 9:27 [QUERY]: Is using CPU hotplug right for isolating CPUs? Viresh Kumar
2014-01-15 10:38 ` Peter Zijlstra
2014-01-15 10:47 ` Viresh Kumar
2014-01-15 11:34 ` Peter Zijlstra [this message]
2014-02-28 9:04 ` Viresh Kumar
2014-01-15 17:17 ` Frederic Weisbecker
[not found] ` <CAKohponEZydR1OmP2xziA9bc3OJPgP3bFmuWFQmrmeQFZccMVQ@mail.gmail.com>
2014-01-16 9:46 ` Thomas Gleixner
2014-01-20 11:30 ` Viresh Kumar
2014-01-20 15:51 ` Frederic Weisbecker
2014-01-21 10:33 ` Viresh Kumar
2014-01-23 14:58 ` Frederic Weisbecker
2014-01-24 5:21 ` Viresh Kumar
2014-01-24 8:29 ` Mike Galbraith
2014-01-28 13:23 ` Frederic Weisbecker
2014-01-28 16:11 ` Kevin Hilman
2014-02-03 8:26 ` Viresh Kumar
2014-02-11 8:52 ` Viresh Kumar
2014-02-13 14:20 ` Frederic Weisbecker
2014-01-20 13:59 ` Lei Wen
2014-01-20 15:00 ` Viresh Kumar
2014-01-20 15:41 ` Frederic Weisbecker
2014-01-21 2:07 ` Lei Wen
2014-01-21 9:50 ` Viresh Kumar
2014-01-23 13:54 ` Frederic Weisbecker
2014-01-23 14:27 ` Viresh Kumar
2014-01-21 9:49 ` Viresh Kumar
2014-01-23 14:01 ` Frederic Weisbecker
2014-01-24 8:53 ` Viresh Kumar
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=20140115113406.GC31570@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=amit.kucheria@linaro.org \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linaro-networking@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.