From: Dario Faggioli <raistlin@linux.it>
To: Stefani Seibold <stefani@seibold.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: SCHED_FIFO and SCHED_RR broken by cfs
Date: Mon, 18 Aug 2008 00:15:26 +0200 [thread overview]
Message-ID: <1219011326.25992.19.camel@Palanthas> (raw)
In-Reply-To: <1218922190.3747.6.camel@matrix>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Sat, 2008-08-16 at 23:29 +0200, Stefani Seibold wrote:
> After disabling kernel support for "Group CPU scheduler" and applying
> 'echo -1 > /proc/sys/kernel/sched_rt_runtime_us' the behaviour is as
> expected.
>
> chrt -f 99 ./a.out
>
> average:13 usec
> min. jitter:0 usec
> max. jitter:29 usec
>
> chrt -o 0 ./a.out
> average:153 usec
> min. jitter:0 usec
> max. jitter:37035 usec
>
> So the problem is located first in the new sched_rt_runtime_us default
> value and second in the "Group CPU scheduler".
Well, if you have group scheduling configured I think you should do both
# echo -1 > /proc/sys/kernel/sched_rt_runtime_us
# echo -1 > /dev/cgroup/cpu.rt_runtime_us
if /dev/cgroup is the mount point of the cgroup file system.
In situations like the one you are describing, this worked for me...
Hope that it also helps you! :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>>
(Raistlin Majere, DragonLance Chronicles -Dragons of Spring Drawning-)
----------------------------------------------------------------------
Dario Faggioli
GNU/Linux Registered User: #340657
Web: http://www.linux.it/~raistlin
Blog: http://blog.linux.it/raistlin
SIP Account: dario.faggioli@sipproxy.wengo.fr or
raistlin@ekiga.net
Jabber Account: dario.faggioli@jabber.org/WengoPhone
GnuPG Key ID: 4DC83AC4
GnuPG Key Fingerprint: 2A78 AD5D B9CF A082 0836 08AD 9385 DA04 4DC8 3AC4
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-08-17 22:15 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 [this message]
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
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=1219011326.25992.19.camel@Palanthas \
--to=raistlin@linux.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stefani@seibold.net \
/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.