From: Venkatesh Pallipadi <venki@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Paul Turner <pjt@google.com>,
Mike Galbraith <efault@gmx.de>, Rik van Riel <riel@redhat.com>,
Venkatesh Pallipadi <venki@google.com>
Subject: [PATCH 0/2] sched: Avoid frequent cross taskgroup switches -v2
Date: Wed, 13 Apr 2011 18:21:08 -0700 [thread overview]
Message-ID: <1302744070-30079-1-git-send-email-venki@google.com> (raw)
In-Reply-To: <AANLkTi=ao5dci3gb=+UmegZx_ag_X6gAFZ5mBb+8=9hR@mail.gmail.com>
As I did not hear any other comments on v1, I am assuming that the
above mentioned case of giving buddy privilege to a SCHED_IDLE task
from one cgroup when there is a non SCHED_IDLE task in other cgroup
is not an important case to handle and keeping this change simpler is better.
So, I am going with Paul's suggestion of sticking with original change,
with some cleanups to handle the frequent CR3 switches problem.
Here is the v2 version of the change, split into two patches.
Signed-off-by: Venkatesh Pallipadi <venki@google.com>
next prev parent reply other threads:[~2011-04-14 1:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 23:33 [PATCH] sched: next buddy hint on sleep and preempt path Venkatesh Pallipadi
2011-03-02 2:44 ` Rik van Riel
2011-03-02 5:43 ` Paul Turner
2011-03-02 6:47 ` Mike Galbraith
2011-03-02 7:08 ` Paul Turner
2011-03-02 7:40 ` Mike Galbraith
2011-03-02 19:12 ` Venkatesh Pallipadi
2011-03-08 0:59 ` [PATCH] sched: next buddy hint on sleep and preempt path - v1 Venkatesh Pallipadi
2011-03-08 1:29 ` Paul Turner
2011-03-08 1:47 ` Venkatesh Pallipadi
2011-04-14 1:21 ` Venkatesh Pallipadi [this message]
2011-04-14 1:21 ` [PATCH 1/2] sched: Make set_*_buddy work on non-task entity -v2 Venkatesh Pallipadi
2011-04-19 12:05 ` [tip:sched/core] sched: Make set_*_buddy() work on non-task entities tip-bot for Venkatesh Pallipadi
2011-04-14 1:21 ` [PATCH 2/2] sched: next buddy hint on sleep and preempt path -v2 Venkatesh Pallipadi
2011-04-14 10:50 ` Peter Zijlstra
2011-04-14 17:30 ` Venkatesh Pallipadi
2011-04-15 21:45 ` Rik van Riel
2011-04-19 12:05 ` [tip:sched/core] sched: Next buddy hint on sleep and preempt path tip-bot for Venkatesh Pallipadi
2011-03-08 2:33 ` [PATCH] sched: next buddy hint on sleep and preempt path - v1 Venkatesh Pallipadi
2011-03-02 19:22 ` [PATCH] sched: next buddy hint on sleep and preempt path Venkatesh Pallipadi
2011-03-02 10:31 ` Peter Zijlstra
2011-03-02 15:25 ` Mike Galbraith
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=1302744070-30079-1-git-send-email-venki@google.com \
--to=venki@google.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=riel@redhat.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®