From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: What's new in sched.git for v2.6.28
Date: Wed, 8 Oct 2008 23:53:00 +0200 [thread overview]
Message-ID: <20081008215300.GA18634@elte.hu> (raw)
the scheduler family of trees had 4 topic trees active during the past 3
months of the v2.6.28 development cycle:
sched/core
sched/cpu-hotplug
sched/cpusets
sched/rt
31 files changed, 688 insertions(+), 487 deletions(-)
38 commits from 18 authors - see the shortlog below.
Ingo
---------------->
Amit K. Arora (1):
sched: minor optimizations in wake_affine and select_task_rq_fair
Andrew Morton (1):
sched: clarify ifdef tangle
Bharata B Rao (2):
sched: call resched_task() conditionally from new task wake up path
sched: maintain only task entities in cfs_rq->tasks list
Chris Friesen (1):
sched: fix list traversal to use _rcu variant
Claudio Scordino (1):
sched: new documentation about CFS
Dario Faggioli (1):
sched_rt.c: resch needed in rt_rq_enqueue() for the root rt_rq
Frederic Weisbecker (1):
cpusets: scan_for_empty_cpusets(), cpuset doesn't seem to be so const
Gautham R Shenoy (1):
sched: fix __load_balance_iterator() for cfq with only one task
Ingo Molnar (3):
sched: clean up __might_sleep()
sched: extract walk_tg_tree(), fix
sched: turn off WAKEUP_OVERLAP
Joe Korty (1):
make might_sleep() display the oopsing process
Kevin Diggs (1):
sched: add kernel doc for the completion, fix kernel-doc-nano-HOWTO.txt
Krzysztof Helt (1):
sched: compilation fix with gcc 3.4.6
Li Zefan (1):
sched: remove redundant code in cpu_cgroup_create()
Manfred Spraul (2):
kernel/cpu.c: Move the CPU_DYING notifiers
kernel/cpu.c: create a CPU_STARTING cpu_chain notifier
Martin Steigerwald (1):
CFS scheduler: documentation about scheduling policies
Oleg Nesterov (3):
sched: do_wait_for_common: use signal_pending_state()
wait_task_inactive(): don't consider task->nivcsw
wait_task_inactive: "improve" the returned value for ->nvcsw == 0
Peter Zijlstra (12):
sched: rt-bandwidth for user grouping interface
sched: rt-bandwidth accounting fix
sched: rt-bandwidth group disable fixes
sched: extract walk_tg_tree()
sched: rt-bandwidth fixes
sched: wakeup preempt when small overlap
sched: rework wakeup preemption
sched: fixlet for group load balance
sched: add some comments to the bandwidth code
sched: more sanity checks on the bandwidth settings
sched: fixup buddy selection
sched: sync wakeups vs avg_overlap
Richard Kennedy (3):
sched: reorder signal_struct to remove 8 bytes on 64 bit builds
sched: reorder struct sched_rt_entity to remove padding on 64 bit builds
reorder struct prop_local_single to remove padding on 64 bit builds
reply other threads:[~2008-10-08 21:53 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=20081008215300.GA18634@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®