public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7
Date: Mon, 19 Nov 2007 19:52:37 +0100	[thread overview]
Message-ID: <20071119185237.GA10965@elte.hu> (raw)
In-Reply-To: <20071119181207.GA11900@codepoet.org>


* Erik Andersen <andersen@codepoet.org> wrote:

> On Mon Nov 19, 2007 at 04:17:56PM +0100, Ingo Molnar wrote:
> > 
> > By popular demand, here is release -v24 of the CFS scheduler patch.
> > 
> > It is a full backport of the latest & greatest scheduler code to 
> > v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7. The patches can be 
> > downloaded from the usual place:
> > 
> >     http://people.redhat.com/mingo/cfs-scheduler/
> 
> Doesn't compile with 2.6.21.7:

does the patch below help?

	Ingo

Index: linux-cfs-2.6.21.7.q/include/linux/sched.h
===================================================================
--- linux-cfs-2.6.21.7.q.orig/include/linux/sched.h
+++ linux-cfs-2.6.21.7.q/include/linux/sched.h
@@ -10,7 +10,7 @@
 #define COMPAT_REGISTER_SYSCTL
 
 /* backporting helper macro: */
-#define cpu_sibling_map(cpu) per_cpu(cpu_sibling_map, cpu)
+#define cpu_sibling_map(cpu) cpu_sibling_map[cpu]
 
 /*
  * cloning flags:


  reply	other threads:[~2007-11-19 18:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 15:17 [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7 Ingo Molnar
2007-11-19 16:04 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8,v2.6.22.13, v2.6.21.7 Fortier,Vincent [Montreal]
2007-11-19 18:59   ` Ingo Molnar
2007-11-19 18:12 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7 Erik Andersen
2007-11-19 18:52   ` Ingo Molnar [this message]
2007-11-19 19:24     ` Erik Andersen
2007-11-19 19:46     ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3,v2.6.23.8, " Fortier,Vincent [Montreal]
2007-11-20 11:24 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, " Damien Wyart
2007-11-20 12:41   ` Srivatsa Vaddagiri
2007-11-20 12:55   ` Ingo Molnar
2007-11-20 13:22     ` Damien Wyart
2007-11-20 20:00 ` Vincent Fortier
2007-11-20 20:38 ` Fabio Comolli
2007-11-20 20:41   ` Ingo Molnar
2007-11-20 20:47     ` Fabio Comolli
2007-11-20 21:53       ` Ingo Molnar
2007-11-21  8:50         ` Fabio Comolli
2007-11-21 10:39           ` Ingo Molnar
2007-11-21 11:11             ` Fabio Comolli
2007-11-26 20:59 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.9, " Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2007-11-19 18:25 [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8,v2.6.22.13, v2.6.21.7 David
2007-11-19 18:57 ` Ingo Molnar
2007-11-19 19:51   ` David
2007-11-19 20:44     ` Ingo Molnar
2007-11-19 20:50     ` Ingo Molnar
2007-11-19 21:39       ` David
2007-11-20  6:13         ` Ingo Molnar
2007-11-20  9:23           ` David
2007-11-20 22:48 [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7 Matthew
2007-11-20 22:59 ` Ingo Molnar
2007-11-23  8:23 Durand
2007-11-23 12:23 ` Ingo Molnar
2007-11-23 16:44   ` Durand

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=20071119185237.GA10965@elte.hu \
    --to=mingo@elte.hu \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.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