From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Turner <pjt@google.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH -tip 0/3] sched: some fixes for vruntime calculation related to cgroup movement(v2)
Date: Mon, 19 Dec 2011 11:55:08 +0900 [thread overview]
Message-ID: <20111219115508.0d5bc98d.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20111215143506.335e443e.nishimura@mxp.nes.nec.co.jp>
Someone who have comments ?
If there are some problems that prevent these patches from being accepted,
I'll fix them.
Thanks,
Daisuke Nishimura
On Thu, 15 Dec 2011 14:35:06 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> Hi, all.
>
> This is an updated version based on comments and rebased onto the -tip tree.
>
> These patches fix problems I could see in 3.2-rc2 when testing frequent cgroup movement
> under very high load. Without these patches, some processes were not scheduled
> (although they were queued into rq)for a very long time(minutes or hours!),
> because vruntime of these processes were far bigger than min_vruntime.
>
> Daisuke Nishimura (3):
> sched: fix cgroup movement of newly created process
> sched: fix cgroup movement of forking process
> sched: fix cgroup movement of waking process
>
> kernel/sched/fair.c | 22 ++++++++++++++++++++--
> 1 files changed, 20 insertions(+), 2 deletions(-)
>
> Thanks,
> Daisuke Nishimura.
prev parent reply other threads:[~2011-12-19 3:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:57 [PATCH 0/3] sched: some fixes for vruntime calculation related to cgroup movement Daisuke Nishimura
2011-12-13 6:57 ` [PATCH 1/3] sched: fix cgroup movement of newly created process Daisuke Nishimura
2011-12-13 12:01 ` Paul Turner
2011-12-14 1:04 ` Daisuke Nishimura
2011-12-13 12:41 ` Peter Zijlstra
2011-12-14 1:05 ` Daisuke Nishimura
2011-12-13 6:58 ` [PATCH 2/3] sched: fix cgroup movement of forking process Daisuke Nishimura
2011-12-13 12:22 ` Paul Turner
2011-12-13 6:59 ` [PATCH 3/3] sched: fix cgroup movement of waking process Daisuke Nishimura
2011-12-13 12:24 ` Paul Turner
2011-12-15 5:35 ` [PATCH -tip 0/3] sched: some fixes for vruntime calculation related to cgroup movement(v2) Daisuke Nishimura
2011-12-15 5:36 ` [PATCH 1/3] sched: fix cgroup movement of newly created process Daisuke Nishimura
2011-12-21 11:45 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-15 5:36 ` [PATCH 2/3] sched: fix cgroup movement of forking process Daisuke Nishimura
2011-12-21 11:44 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-21 17:26 ` Tejun Heo
2011-12-21 17:37 ` Tejun Heo
2011-12-22 1:54 ` Frederic Weisbecker
2011-12-22 2:01 ` Tejun Heo
2011-12-15 5:37 ` [PATCH 3/3] sched: fix cgroup movement of waking process Daisuke Nishimura
2011-12-21 11:45 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-19 2:55 ` Daisuke Nishimura [this message]
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=20111219115508.0d5bc98d.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=a.p.zijlstra@chello.nl \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.com \
/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®