From: Andreas Jaeger <aj@suse.de>
To: Nicholas Miell <nmiell@attbi.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [announce] [patch] batch/idle priority scheduling, SCHED_BATCH
Date: Mon, 01 Jul 2002 08:48:51 +0200 [thread overview]
Message-ID: <ho1yaodju4.fsf@gee.suse.de> (raw)
In-Reply-To: <1025492120.12685.8.camel@entropy> (Nicholas Miell's message of "30 Jun 2002 19:55:18 -0700")
Nicholas Miell <nmiell@attbi.com> writes:
> On Sun, 2002-06-30 at 17:26, Ingo Molnar wrote:
>
>> -#define SCHED_OTHER 0
>> +#define SCHED_NORMAL 0
>
>>From IEEE 1003.1-2001 / Open Group Base Spec. Issue 6:
> "Conforming implementations shall include one scheduling policy
> identified as SCHED_OTHER (which may execute identically with either the
> FIFO or round robin scheduling policy)."
>
> So, you probably want to add a "#define SCHED_OTHER SCHED_NORMAL" here
> in order to prevent future confusion, especially because the user-space
> headers have SCHED_OTHER, but no SCHED_NORMAL.
This can be done in glibc. linux/sched.h should not be used by
userspace applications, glibc has the define in <bits/sched.h> which
is included from <sched.h> - and <sched.h> is the file defined by
Posix.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-07-01 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 0:26 [announce] [patch] batch/idle priority scheduling, SCHED_BATCH Ingo Molnar
2002-07-01 2:55 ` Nicholas Miell
2002-07-01 6:48 ` Andreas Jaeger [this message]
2002-07-01 8:00 ` Ingo Molnar
2002-07-02 0:02 ` Nicholas Miell
2002-07-03 7:59 ` Ingo Molnar
2002-07-04 13:04 ` Vitez Gabor
2002-07-07 12:46 ` Jakob Oestergaard
2002-07-07 19:07 ` Bernd Eckenfels
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=ho1yaodju4.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nmiell@attbi.com \
--cc=torvalds@transmeta.com \
/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