From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH] sched/rt: Use IPI to trigger RT task push migration instead of pulling
Date: Fri, 06 Feb 2015 16:58:08 +0100 [thread overview]
Message-ID: <1423238288.3377.83.camel@gmail.com> (raw)
In-Reply-To: <20150206124051.GN21418@twins.programming.kicks-ass.net>
On Fri, 2015-02-06 at 13:40 +0100, Peter Zijlstra wrote:
> On Thu, Feb 05, 2015 at 11:04:20AM -0500, Steven Rostedt wrote:
> Well, the thing is, with or without this patch, the worst case is still
> the very same. The likelihood of actually triggering it goes down
> dramatically [*], but any spin_lock() has that O(nr_cpus) worst case, and
> that spinlock op isn't going away.
>
> Now, lowering avg/median cases is good, but don't kid yourself that the
> worst case is going to be better.
>
> People running -RT on big boxes had better be aware of this.
The folks I know of running -RT on big boxen isolate cores and nail
absolutely everything to the floor. The only way to survive in a big
box is to chop the thing into tiny pieces. A plasma cutter would be
even better.. 'course you could just _buy smaller boxen_ and connect
what you want connected, take the lazy path to big box solution ;-)
-Mike
next prev parent reply other threads:[~2015-02-06 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 19:39 [RFC][PATCH] sched/rt: Use IPI to trigger RT task push migration instead of pulling Steven Rostedt
2015-02-05 14:58 ` Peter Zijlstra
2015-02-05 16:04 ` Steven Rostedt
2015-02-06 12:40 ` Peter Zijlstra
2015-02-06 15:58 ` Mike Galbraith [this message]
2015-02-05 15:21 ` Peter Zijlstra
2015-02-05 16:55 ` Steven Rostedt
2015-02-06 13:23 ` Peter Zijlstra
2015-02-06 13:59 ` Peter Zijlstra
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=1423238288.3377.83.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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.