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, -v15
Date: Thu, 31 May 2007 17:09:08 +0200 [thread overview]
Message-ID: <20070531150908.GA23538@elte.hu> (raw)
i'm pleased to announce release -v15 of the CFS scheduler patchset.
The CFS rolled-up patch against v2.6.22-rc3, v2.6.22-rc3-mm1,
v2.6.21.1/3 or v2.6.20.10 can be downloaded from the usual place:
http://people.redhat.com/mingo/cfs-scheduler/
-v15 includes smaller fixes only. More precise sched_info statistics
from Balbir Singh, interactivity tweaks from Mike Galbraith and a number
of corner-cases fixed/cleaned up by Dmitry Adamushko.
Changes since -v14:
- more precise sched_info statistics (Balbir Singh)
- call update_curr() when preempting to an RT task (Dmitry Adamushko)
- smaller interactivity tweaks (Mike Galbraith)
- apply runtime-limit to yield_to() as well (Dmitry Adamushko)
- load-balancing iterator cleanup/simplification (Dmitry Adamushko)
- fix code duplication (noticed by Li Yu)
- cleanups (Mike Galbraith)
- fix CPU usage accounting of threadeded apps in 'top'
- more cleanups
As usual, any sort of feedback, bugreport, fix and suggestion is more
than welcome!
Ingo
next reply other threads:[~2007-05-31 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 15:09 Ingo Molnar [this message]
2007-06-06 6:42 ` [patch] CFS scheduler, -v15 Srivatsa Vaddagiri
2007-06-06 7:01 ` Ingo Molnar
2007-06-06 7:43 ` Srivatsa Vaddagiri
2007-06-06 9:08 ` Dmitry Adamushko
2007-06-06 10:37 ` Balbir Singh
2007-06-06 10:59 ` Srivatsa Vaddagiri
2007-06-06 11:19 ` Dmitry Adamushko
2007-06-06 11:37 ` Srivatsa Vaddagiri
2007-06-06 11:46 ` Srivatsa Vaddagiri
2007-06-14 12:43 ` Srivatsa Vaddagiri
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=20070531150908.GA23538@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 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.