public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Esben Nielsen <nielsen.esben@googlemail.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Where is RLIMIT_RT_CPU?
Date: Sat, 15 Jul 2006 09:58:15 -0400	[thread overview]
Message-ID: <1152971896.16617.4.camel@mindpipe> (raw)
In-Reply-To: <1152919240.6374.38.camel@idefix.homelinux.org>

On Sat, 2006-07-15 at 09:20 +1000, Jean-Marc Valin wrote:
> > Can't you just make a prio 1 task which signals a prio 99 once say every 
> > second. If the priority 99 task doesn't get the signal after say 2 
> > seconds, it will look for a rt task running wild. At worst it will have to do
> > an O(n) algorith when things have gone wrong, not when everything is 
> > working.
> 
> Well, that would work in sort of preventing a complete lockup, but the
> watchdog wouldn't even know if the task eating lots of CPU is privileged
> (OK) or unprivileged (not OK). Also, the original RLIMIT_RT_CPU feature
> allowed you to really control how much CPU is available to unprivileged
> users, not just prevent them from getting 100% CPU. 

Non-root RT tasks are not "unprivileged" - they have a level of
privileges between a normal user and root.  Really I think it's OK for
these tasks to consume 100% CPU, as the admin has explicitly allowed it.

The only problem is that Ubuntu shipped with this enabled for everyone.

Lee


  reply	other threads:[~2006-07-15 13:58 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
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 [this message]
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=1152971896.16617.4.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=Jean-Marc.Valin@USherbrooke.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nielsen.esben@googlemail.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