From: Eric St-Laurent <ericstl34@sympatico.ca>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
mingo@elte.hu, pwil3058@bigpond.net.au,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: avoid large irq-latencies in smp-balancing
Date: Wed, 07 Nov 2007 19:24:46 -0500 [thread overview]
Message-ID: <1194481486.6606.6.camel@perkele> (raw)
In-Reply-To: <20071107221007.GA31008@goodmis.org>
On Wed, 2007-11-07 at 17:10 -0500, Steven Rostedt wrote:
> >
> > It would be nice if sched_nr_migrate didn't exist, really. It's hard to
> > imagine anyone wanting to tweak it, apart from developers.
>
> I'm not so sure about that. It is a tunable for RT. That is we can tweak
> this value to be smaller if we don't like the latencies it gives us.
>
> This is one of those things that sacrifices performance for latency.
> The higher the number, the better it can spread tasks around, but it
> also causes large latencies.
>
> I've just included this patch into 2.6.23.1-rt11 and it brought down an
> unbounded latency to just 42us. (previously we got into the
> milliseconds!).
>
> Perhaps when this feature matures, we can come to a good defined value
> that would be good for all. But until then, I recommend keeping this a
> tunable.
Why not use the latency-expectation infrastructure?
Iterate under lock until (or before...) the system global latency is
respected.
- Eric
next prev parent reply other threads:[~2007-11-08 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:29 [PATCH] sched: avoid large irq-latencies in smp-balancing Peter Zijlstra
2007-11-07 12:17 ` Peter Zijlstra
2007-11-07 18:27 ` Andrew Morton
2007-11-07 18:58 ` Peter Zijlstra
2007-11-07 22:10 ` Steven Rostedt
2007-11-08 0:24 ` Eric St-Laurent [this message]
2007-11-08 4:37 ` Gregory Haskins
2007-11-09 13:09 ` Nick Piggin
2007-11-09 12:41 ` DM
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=1194481486.6606.6.camel@perkele \
--to=ericstl34@sympatico.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pwil3058@bigpond.net.au \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox