From: Nicholas Miell <nmiell@attbi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andreas Jaeger <aj@suse.de>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [announce] [patch] batch/idle priority scheduling, SCHED_BATCH
Date: 01 Jul 2002 17:02:21 -0700 [thread overview]
Message-ID: <1025568143.1673.4.camel@entropy> (raw)
In-Reply-To: <Pine.LNX.4.44.0207010954420.2321-100000@e2>
On Mon, 2002-07-01 at 01:00, Ingo Molnar wrote:
>
> On Mon, 1 Jul 2002, Andreas Jaeger wrote:
> > 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.
>
> yes, this was my thinking too.
OK, I can understand that line of reasoning.
Keep in mind that someday, someone who is looking for the implementation
of the SCHED_OTHER policy will be thoroughly confused by the kernel's
complete lack of reference to SCHED_OTHER. And they'll be asking you for
clarification.
Or, you could make some note in the source that SCHED_OTHER is
SCHED_NORMAL and eliminate any source of confusion now.
- Nicholas
next prev parent reply other threads:[~2002-07-02 0:00 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
2002-07-01 8:00 ` Ingo Molnar
2002-07-02 0:02 ` Nicholas Miell [this message]
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=1025568143.1673.4.camel@entropy \
--to=nmiell@attbi.com \
--cc=aj@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.