From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: [patch] CFS scheduler, -v16
Date: Fri, 8 Jun 2007 21:58:40 +0200 [thread overview]
Message-ID: <20070608195840.GA14928@elte.hu> (raw)
i'm pleased to announce release -v16 of the CFS scheduler patchset.
The rolled-up CFS patch against v2.6.22-rc4, v2.6.22-rc4-mm2, v2.6.21.4
or v2.6.20.13 can be downloaded from the usual place:
http://people.redhat.com/mingo/cfs-scheduler/
-v16 includes smaller fixes. Continued work on precise /proc CPU
accounting of both SCHED_OTHER and RT tasks by Dmitry Adamushko and
Balbir Singh. Reniced tasks should now disturb nice-0 tasks even less.
Also, i have changed SCHED_BATCH back to its current mainline meaning
and have added a SCHED_IDLEPRIO instead (first introduced by Con Kolivas
in staircase/RSDL/SD).
Changes since -v15:
- more /proc CPU stats accounting improvements (Dmitry Adamushko,
Balbir Singh)
- fix SCHED_BATCH (reported by Con Kolivas)
- update_load_fair() - use 64-bit arithmetics (Dmitry Adamushko)
- fix RT->NORMAL accounting issue raised by Srivatsa Vaddagiri: have
correct exec_start stamping. (Dmitry Adamushko)
- check for negative deltas in task_sched_runtime() (Dmitry Adamushko)
- check for large forward-jumping sched_clock()
- cleanup: remove task_struct :: last_ran (Dmitry Adamushko)
- /proc/sched_debug printk fixes (Andrew Morton)
- add SCHED_IDLEPRIO
- consolidate the granularity settings and make them scale together
- improve /proc/sched_debug output
- remove the yield workarounds - the default seems to be working now.
- introduce lower and upper limits for the granularity tunables.
Setting them to zero accidentally broke nice levels.
- various small fixes/cleanups
As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome!
Ingo
reply other threads:[~2007-06-08 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070608195840.GA14928@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox