From: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Where is RLIMIT_RT_CPU?
Date: Fri, 14 Jul 2006 19:39:11 +1000 [thread overview]
Message-ID: <1152869952.6374.8.camel@idefix.homelinux.org> (raw)
In-Reply-To: <1152809039.8237.48.camel@mindpipe>
> It was not merged.
>
> This problem should be addressed by a userspace RT watchdog. Ubuntu
> should not have shipped their system with unlimited non-root realtime
> enabled and no watchdog.
Does such a daemon currently exist? Even then, is there any way to
police all unprivileged RT apps without introducing an O(N) operation
running continuously at max rt priority? Sort of defeats the purpose of
having an O(1) scheduler, no? I assume the RT check can be some in O(1)
time in the kernel, right?
About Ubuntu, I agree it wasn't a smart thing to do (I'm not an Ubuntu
devel, so I don't know what the reason was), but it would be nice if
this could be fixed without having to entirely remove the unprivileged
real-time feature. In the end, I'm not sure what the best solution is
(just an RT audio developer).
Jean-Marc
next prev parent reply other threads:[~2006-07-14 9:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 0:23 Jean-Marc Valin
2006-07-13 16:43 ` Lee Revell
2006-07-14 9:39 ` Jean-Marc Valin [this message]
2006-07-14 21:31 ` Esben Nielsen
2006-07-14 23:20 ` Jean-Marc Valin
2006-07-15 13:58 ` Lee Revell
2006-07-15 14:19 ` Jean-Marc Valin
2006-07-15 14:42 ` Arjan van de Ven
2006-07-15 15:04 ` Jean-Marc Valin
2006-07-15 15:44 ` Lee Revell
2006-07-16 0:23 ` Jean-Marc Valin
2006-07-16 10:44 ` Esben Nielsen
2006-07-16 10:14 ` Jean-Marc Valin
2006-07-16 12:20 ` Esben Nielsen
2006-07-17 11:53 ` Jean-Marc Valin
2006-07-17 13:59 ` Steven Rostedt
2006-07-17 14:32 ` Jean-Marc Valin
2006-07-17 15:06 ` Steven Rostedt
2006-07-17 16:18 ` Esben Nielsen
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=1152869952.6374.8.camel@idefix.homelinux.org \
--to=jean-marc.valin@usherbrooke.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®