From: Andrew Morton <akpm@linux-foundation.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH][ 3/5] sched: implement staircase deadline cpu scheduler
Date: Mon, 26 Mar 2007 20:47:23 -0800 [thread overview]
Message-ID: <20070326204723.af7203af.akpm@linux-foundation.org> (raw)
In-Reply-To: <200703271210.39429.kernel@kolivas.org>
On Tue, 27 Mar 2007 13:10:39 +1100 Con Kolivas <kernel@kolivas.org> wrote:
> + DECLARE_BITMAP(bitmap, PRIO_RANGE + 1);
> + /*
> + * This bitmap shows what priorities this task has received quota
> + * from for this major priority rotation on its current runqueue.
> + */
> struct prio_array *array;
> + unsigned long rotation;
> + /* Which major runqueue rotation did this task run */
>
> unsigned short ioprio;
> #ifdef CONFIG_BLK_DEV_IO_TRACE
> unsigned int btrace_seq;
> #endif
> - unsigned long sleep_avg;
> unsigned long long timestamp, last_ran;
> unsigned long long sched_time; /* sched_clock time spent running */
> - enum sleep_type sleep_type;
>
> unsigned long policy;
> cpumask_t cpus_allowed;
> - unsigned int time_slice, first_time_slice;
> + int time_slice;
> + /*
> + * How much this task is entitled to run at the current priority
> + * before being requeued at a lower priority.
> + */
> + unsigned int first_time_slice;
> + /* Is this the very first time_slice this task has ever run. */
> + int quota;
> + /* How much this task receives at each priority level */
This is nuts. Nobody puts the description of the fields _below_ those fields.
I fixed it in my copy (while fixing the usual reject storm). Please fix it
in your tree, wherever it occurs.
Weird.
next prev parent reply other threads:[~2007-03-27 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 2:10 [PATCH][ 3/5] sched: implement staircase deadline cpu scheduler Con Kolivas
2007-03-27 4:47 ` Andrew Morton [this message]
2007-03-27 5:23 ` Mike Galbraith
2007-04-30 18:50 ` Andrew Morton
2007-05-02 12:23 ` Con Kolivas
2007-05-02 15:51 ` Henrique de Moraes Holschuh
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=20070326204723.af7203af.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--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