From: Peter Zijlstra <peterz@infradead.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "Torvalds, Linus" <torvalds@linux-foundation.org>,
Stefani Seibold <stefani@seibold.net>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: SCHED_FIFO and SCHED_RR broken by cfs
Date: Mon, 18 Aug 2008 13:51:55 +0200 [thread overview]
Message-ID: <1219060315.10800.338.camel@twins> (raw)
In-Reply-To: <200808182124.17359.nickpiggin@yahoo.com.au>
On Mon, 2008-08-18 at 21:24 +1000, Nick Piggin wrote:
> Really, you think the enterprise distros will willingly break POSIX
> and their own backwards compatiblity by default? I wouldn't have
> thought so, but anyway I guess they are free to make that choice, so
> where's the problem?
I'm not seeing why you're making such a big fuss over this - IMO its not
such a significant breakage. Esp since very few realtime apps will
require such large amounts of time to ever run into the throttle.
If their usage is 95%+ cpu they must have magic WCET estamates - or like
in this case, be a benchmark app which IMHO just abuses the real-time
class.
It's like running your real-time code on a 5% slower cpu - if it runs
correctly on the 5% slower cpu, it will run correctly here too.
Note that correctness from a RT pov is making your deadline.
next prev parent reply other threads:[~2008-08-18 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 9:55 SCHED_FIFO and SCHED_RR broken by cfs Stefani Seibold
2008-08-16 14:53 ` Peter Zijlstra
2008-08-16 16:26 ` Stefani Seibold
2008-08-16 21:29 ` Stefani Seibold
2008-08-17 22:15 ` Dario Faggioli
2008-08-18 10:47 ` [PATCH] sched: rt-bandwidth disable fixes Peter Zijlstra
2008-08-18 11:11 ` Peter Zijlstra
2008-08-17 13:04 ` SCHED_FIFO and SCHED_RR broken by cfs Nick Piggin
2008-08-18 10:50 ` Peter Zijlstra
2008-08-18 10:58 ` Nick Piggin
2008-08-18 11:09 ` Peter Zijlstra
2008-08-18 11:24 ` Nick Piggin
2008-08-18 11:51 ` Peter Zijlstra [this message]
2008-08-18 12:14 ` Nick Piggin
2008-08-18 18:01 ` Max Krasnyansky
2008-08-18 19:46 ` Peter Zijlstra
2008-08-19 7:44 ` Nick Piggin
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=1219060315.10800.338.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nickpiggin@yahoo.com.au \
--cc=stefani@seibold.net \
--cc=torvalds@linux-foundation.org \
/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.