From: Peter Zijlstra <peterz@infradead.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
"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 21:46:15 +0200 [thread overview]
Message-ID: <1219088775.10800.355.camel@twins> (raw)
In-Reply-To: <48A9B906.7090201@qualcomm.com>
On Mon, 2008-08-18 at 11:01 -0700, Max Krasnyansky wrote:
> Just wanted to mention that I'm with Nick on this one. I pointed this
> (ie POSIX breakage) out as soon as the change went in. I do have a valid
> (which some people disagree with ;-)) workload that uses 100% of the
> CPU. So my unit-tests caught this right away.
>
> Anyway, "RT bandwidth throttling" has been in and enabled be default
> since 2.6.25. So I'm not sure if it makes sense to revert the default at
> this point.
Already working on a patches to make it so..
The patch to change the default is simple enough - but I spotted a few
other bugs while poking at the issue Dario pointed out.
next prev parent reply other threads:[~2008-08-18 19:52 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
2008-08-18 12:14 ` Nick Piggin
2008-08-18 18:01 ` Max Krasnyansky
2008-08-18 19:46 ` Peter Zijlstra [this message]
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=1219088775.10800.355.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--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.