From: "Bhavesh P. Davda" <bhavesh@avaya.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] SCHED_FIFO and SCHED_RR scheduler fix, kernel 2.2.21
Date: Fri, 21 Jun 2002 13:10:14 -0600 [thread overview]
Message-ID: <3D137A16.2080303@avaya.com> (raw)
In-Reply-To: E17LSDo-0001KB-00@the-village.bc.nu
Alan Cox wrote:
>>The 2.2.21 kernel was behaving incorrectly for SCHED_FIFO and SCHED_RR
>>scheduling.
>
>
> Looks fine but I dont want to apply behaviour changing non critical stuff
> to 2.2
Oh, no!
What's going on with the kernel community? I posted a similar fix for
the 2.4.18 kernel, and it hasn't been picked up there either.
For the 2.4.18 kernel scheduler, our 86 process application (SCHED_FIFO,
priorities 7-23, System V semaphores for priority preemption) won't even
stay up without my patch.
The 2.2.21 SCHED_FIFO behaviour is correct but slightly inefficient,
while the SCHED_RR behaviour is plain broken. What is an application
that depends on correct SCHED_RR behaviour to do in that case? There are
applications where increased latencies as a result of SCHED_RR being
broken are unacceptable.
--
Bhavesh P. Davda
Avaya Inc
Room B3-B03 E-mail : bhavesh@avaya.com
1300 West 120th Avenue Phone : (303) 538-4438
Westminster, CO 80234 Fax : (303) 538-3155
next prev parent reply other threads:[~2002-06-21 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 22:12 [PATCH] SCHED_FIFO and SCHED_RR scheduler fix, kernel 2.2.21 Bhavesh P. Davda
2002-06-21 17:29 ` Alan Cox
2002-06-21 19:10 ` Bhavesh P. Davda [this message]
2002-06-21 19:56 ` Alan Cox
2002-06-23 9:47 ` Ingo Molnar
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=3D137A16.2080303@avaya.com \
--to=bhavesh@avaya.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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