From: "Bruce Ashfield" <bruce.ashfield@windriver.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] CFS scheduler, -v20, for v2.6.22.5, v2.6.21.7, v2.6.20.16
Date: Thu, 23 Aug 2007 21:43:20 -0400 [thread overview]
Message-ID: <3bd6b93c0708231843m1e94e192i6a806ce18c266f69@mail.gmail.com> (raw)
In-Reply-To: <20070823094346.GA26281@elte.hu>
On 8/23/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> By popular demand, here is release -v20 of the CFS scheduler. It is a
> full backport of the latest & greatest v2.6.23-rc3 CFS code to
> v2.6.22.5, v2.6.21.7 and v2.6.20.16. The patches can be downloaded from
> the usual place:
Ingo,
Great to see the older kernels updated, thanks for the patches.
I've got a bit of a modified 2.6.21.7, but when I built with
CONFIG_FAIR_GROUP_SCHED=y, I need the following change
to make things right (On a quick glance, my change matches the
2.6.23-rc3 code). Then again, I may just be doing something
stupid.
My apologies in advance if gmail decides to mangle the patch.
--- a/kernel/sched_fair.c.orig 2007-08-23 21:25:08.000000000 -0400
+++ a/kernel/sched_fair.c 2007-08-23 21:25:18.000000000 -0400
@@ -1057,7 +1057,7 @@ static void task_new_fair(struct rq *rq,
*/
static void set_curr_task_fair(struct rq *rq)
{
- struct sched_entity *se = &rq->curr.se;
+ struct sched_entity *se = &rq->curr->se;
for_each_sched_entity(se)
set_next_entity(cfs_rq_of(se), se);
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
next prev parent reply other threads:[~2007-08-24 1:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 9:43 Ingo Molnar
2007-08-23 10:25 ` Ingo Molnar
2007-08-23 12:24 ` [patch] CFS scheduler, -v20, for v2.6.22.5, v2.6.21.7,v2.6.20.16 David Schwartz
2007-08-24 14:59 ` Ingo Molnar
2007-08-24 1:43 ` Bruce Ashfield [this message]
2007-08-24 6:09 ` [patch] CFS scheduler, -v20, for v2.6.22.5, v2.6.21.7, v2.6.20.16 Ingo Molnar
2007-08-24 4:59 ` Willy Tarreau
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=3bd6b93c0708231843m1e94e192i6a806ce18c266f69@mail.gmail.com \
--to=bruce.ashfield@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®