From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Carsten Emde <ce@ceag.ch>,
Clark Williams <williams@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Kumar Gala <galak@gate.crashing.org>,
Ralf Baechle <ralf@linux-mips.org>, rostedt <rostedt@goodmis.org>
Subject: Re: On migrate_disable() and latencies
Date: Fri, 22 Jul 2011 16:57:43 +0200 [thread overview]
Message-ID: <1311346663.9642.0.camel@twins> (raw)
In-Reply-To: <1311331798.27400.28.camel@twins>
On Fri, 2011-07-22 at 12:49 +0200, Peter Zijlstra wrote:
> > The scenario is on where you stack N migrate-disable tasks on a run
> > queue (necessarily of increasing priority). Doing this requires all cpus
> > in the system to be as busy, for otherwise the task would simply be
> > moved to another cpu.
>
> This implies it requires at least nr-cpus^2 tasks to pull this off.
OK, scrap that, 2*nr-cpus is enough.
next prev parent reply other threads:[~2011-07-22 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:19 On migrate_disable() and latencies Peter Zijlstra
2011-07-22 10:49 ` Peter Zijlstra
2011-07-22 14:57 ` Peter Zijlstra [this message]
2011-07-22 17:45 ` Nicholas Mc Guire
2011-07-25 8:21 ` Peter Zijlstra
2011-07-23 0:39 ` Paul E. McKenney
2011-07-25 8:30 ` Peter Zijlstra
2011-07-25 21:17 ` Paul E. McKenney
2011-07-27 11:13 ` Peter Zijlstra
2011-07-27 18:30 ` Paul E. McKenney
2011-07-28 5:50 ` Yong Zhang
2011-07-28 7:01 ` Thomas Gleixner
2011-07-28 7:10 ` Yong Zhang
2011-07-28 7:54 ` Nicholas Mc Guire
2011-07-28 12:05 ` Paul E. McKenney
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=1311346663.9642.0.camel@twins \
--to=peterz@infradead.org \
--cc=ce@ceag.ch \
--cc=galak@gate.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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 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.