[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1253625878.6575.34.camel@desktop>
Date: Tue, 22 Sep 2009 06:24:38 -0700
From: Daniel Walker <dwalker@...o99.com>
To: Raistlin <raistlin@...ux.it>
Cc: Peter Zijlstra <peterz@...radead.org>, claudio@...dence.eu.com,
michael@...dence.eu.com, mingo@...e.hu,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
johan.eker@...csson.com, p.faure@...tech.ch,
Fabio Checconi <fabio@...dalf.sssup.it>,
Dhaval Giani <dhaval.giani@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Tommaso Cucinotta <tommaso.cucinotta@...up.it>
Subject: Re: [RFC][PATCH] SCHED_EDF scheduling class
On Tue, 2009-09-22 at 12:30 +0200, Raistlin wrote:
> Hi Peter, Hi all,
>
> this is the implementation of a new scheduling class called
> SCHED_EDF made by me and Michael Trimarchi (CC:-ed). We followed the
> suggestions you gave us at the multicore workshop in Kaiserlsautern
> on October.
>
> For other people: it is a real-time scheduling policy based on the
> Earliest Deadline First (EDF) algorithm, one of the most common
> real-time scheduling algorithms.
You've got some type of encoding corruption in your patch,
+ else {
+ if (!edf_task(p))
+ p->sched_class =3D &fair_sched_class;
+ else
+ p->sched_class =3D &edf_sched_class;
+ }
=20
p->prio =3D prio;
=20
See the =20 , and =3D above.. I'm not sure exactly how that gets into
patches ;( We require utf8 encodings , some people can handle the stuff
above but most scripts and the patch command won't be able to. I realize
this is an RFC , so the next time you submit this try to make it utf8 ..
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists