From: Albert Cahalan <albert@users.sf.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
kernel@kolivas.org, Andrew Morton OSDL <akpm@osdl.org>,
nickpiggin@yahoo.com.au
Subject: Re: SCHED_BATCH and SCHED_BATCH numbering
Date: 05 Aug 2004 05:48:19 -0400 [thread overview]
Message-ID: <1091699297.1232.1809.camel@cube> (raw)
In-Reply-To: <20040805065708.GA10124@elte.hu>
On Thu, 2004-08-05 at 02:57, Ingo Molnar wrote:
> * Albert Cahalan <albert@users.sf.net> wrote:
>
> > Are these going to be numbered consecutively, or might they better be
> > done like the task state? [...]
>
> this is quite unnecessary at the moment since p->prio < MAX_RT_PRIO is a
> good enough check - but whenever the way p->prio works is changed it
> will be easy to introduce a PF_REALTIME flag that is set/cleared in
> setscheduler(). (instead of playing around with p->policy.)
That was one example. I'm guessing that one might want to
test for other policy groupings, like these:
SCHED_RR | SCHED_ISO
SCHED_BATCH | SCHED_NORMAL
SCHED_SPORADIC | SCHED_NORMAL
SCHED_EDF | SCHED_FIFO
If that's certainly not going to be useful, even in the future,
then of course there's no reason to allocate the values as bits.
In any case, it's a user ABI issue, and I'd like to see what
the allocations are going to be. Perhaps I should send in a
patch that just allocates a few of these...?
prev parent reply other threads:[~2004-08-05 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 16:50 SCHED_BATCH and SCHED_BATCH numbering Albert Cahalan
2004-08-05 1:17 ` Peter Williams
2004-08-05 1:27 ` Nick Piggin
2004-08-05 2:09 ` Peter Williams
2004-08-05 2:23 ` Nick Piggin
2004-08-05 3:03 ` Peter Williams
2004-08-05 3:06 ` Nick Piggin
2004-08-05 2:28 ` Albert Cahalan
2004-08-05 7:06 ` Nick Piggin
2004-08-05 3:36 ` Peter Williams
2004-08-05 4:15 ` Nick Piggin
2004-08-05 6:57 ` Ingo Molnar
2004-08-05 9:48 ` Albert Cahalan [this message]
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=1091699297.1232.1809.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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