From: Lee Revell <rlrevell@joe-job.com>
To: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Where is RLIMIT_RT_CPU?
Date: Thu, 13 Jul 2006 12:43:59 -0400 [thread overview]
Message-ID: <1152809039.8237.48.camel@mindpipe> (raw)
In-Reply-To: <1152663825.27958.5.camel@localhost>
On Wed, 2006-07-12 at 10:23 +1000, Jean-Marc Valin wrote:
> Hi,
>
> I saw many references to RLIMIT_RT_CPU (e.g. in
> http://lwn.net/Articles/120797/ ) as a way of limiting the amount of CPU
> an unprivileged task can use at real-time priority. My understand was
> that the feature had been merged into 2.6.12 as part of Ingo's rt-limit
> patches. Unfortunately, I can't find any reference to that on my system
> (latest Ubuntu), so I'm wondering where it's gone. Has it been removed,
> renamed, ...? Considering that Ubuntu Dapper currently allows any user
> to make unlimited use of realtime scheduling, this feature would be
> really useful to prevent user apps from accidently crashing the system.
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.
Lee
next prev parent reply other threads:[~2006-07-13 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 0:23 Where is RLIMIT_RT_CPU? Jean-Marc Valin
2006-07-13 16:43 ` Lee Revell [this message]
2006-07-14 9:39 ` Jean-Marc Valin
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=1152809039.8237.48.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jean-marc.valin@usherbrooke.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.