From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [git pull request] scheduler updates
Date: Fri, 24 Aug 2007 16:12:15 +0200 [thread overview]
Message-ID: <20070824141215.GA24403@elte.hu> (raw)
Linus, please pull the latest scheduler git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git
It includes 8 commits, 3 of which are important: the most important
change is a bugfix to the new task startup penalty code. This could
explain the task-startup unpredictability problem reported by Al Boldi.
Then there's also a change/tweak that increases the default granularity:
it's still well below human perception so should not be noticeable, but
servers win a bit from less preemption of CPU-bound tasks. (this is also
the first step towards eliminating HZ from the granularity default
calculation.)
Plus a bonus balance inconsistency has been fixed: the previous logic
was slightly inflatory of sleeper wait-runtime, without a
counter-balance on runners. (I found no noticeable or measurable impact,
other than a ~5% improvement in hackbench performance [due to less
preemption scheduling] and a slightly nicer looking /proc/sched_debug
output when there are lots of sleepers.)
Five other, low-impact changes: a group-scheduling fixlet from Bruce
Ashfield, two nice simplifications from Peter Zijlstra to the
bonus-balance code (which eliminate a 64-bit multiplication and shrink
the code), a QOI improvement from Dmitry Adamushko to RR RT task
preemption [not strictly required for .23 but this has been in my tree
for some time already with no ill effects and the code is obviously
correct] and a dead code elimination fix from Sven-Thorsten Dietrich.
Test-built and test-booted on x86-32 and x86-64, and it passed a few
dozen "make randconfig" builds as well.
Ingo
------------------>
Bruce Ashfield (1):
sched: CONFIG_SCHED_GROUP_FAIR=y fixlet
Dmitry Adamushko (1):
sched: optimize task_tick_rt() a bit
Ingo Molnar (3):
sched: increase default granularity a bit
sched: tidy up and simplify the bonus balance
sched: fix startup penalty calculation
Peter Zijlstra (2):
sched: simplify bonus calculation #1
sched: simplify bonus calculation #2
Sven-Thorsten Dietrich (1):
sched: simplify can_migrate_task()
sched.c | 6 ------
sched_fair.c | 26 +++++++++++++++-----------
sched_rt.c | 11 ++++++++---
3 files changed, 23 insertions(+), 20 deletions(-)
next reply other threads:[~2007-08-24 14:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 14:12 Ingo Molnar [this message]
2007-08-24 18:09 ` [git pull request] scheduler updates Linus Torvalds
2007-08-24 19:37 ` Ingo Molnar
2007-08-25 17:23 ` Ingo Molnar
2007-08-25 20:43 ` Ingo Molnar
2007-08-25 21:20 ` Peter Zijlstra
2007-08-31 1:58 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2007-08-28 11:32 Ingo Molnar
2007-08-28 14:11 ` Mike Galbraith
2007-08-28 14:46 ` Ingo Molnar
2007-08-28 14:55 ` Mike Galbraith
2007-08-23 16:07 Ingo Molnar
2007-08-12 16:32 Ingo Molnar
2007-08-10 21:22 Ingo Molnar
2007-08-08 20:30 Ingo Molnar
2007-08-02 16:08 Ingo Molnar
2007-07-26 12:08 Ingo Molnar
2007-07-19 16:50 Ingo Molnar
2007-07-16 7:53 Ingo Molnar
2007-07-11 19:38 Ingo Molnar
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=20070824141215.GA24403@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.