From: Steven Rostedt <rostedt@goodmis.org>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Esben Nielsen <nielsen.esben@googlemail.com>,
Lee Revell <rlrevell@joe-job.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Where is RLIMIT_RT_CPU?
Date: Mon, 17 Jul 2006 09:59:13 -0400 [thread overview]
Message-ID: <1153144753.652.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1153137181.24228.16.camel@idefix.homelinux.org>
On Mon, 2006-07-17 at 21:53 +1000, Jean-Marc Valin wrote:
>
> Why not? It could be nice as well if someone wants to implement that.
> I'd already be quite happy to just have basic control on the CPU time.
>
Have you thought about using something like Xen? Have a virtual machine
that you can even give root access to users, and still have control of
the actual physical machine.
> As I mentioned earlier, it's not about total lock-up, but having things
> run relatively smoothly and (if possible?) even fairly.
One issue I think you might have is what exactly is a CPU limit? If the
system is idle, and you have an app that goes into a busy loop, do you
kill it after it hits the limit, even if it isn't RT? Or do you just
force it to schedule? Or do you consider idle a special case? Do you
want just the apps to be limited, or all the apps that belong to a
specific user.
>From this thread, it seems your goal is to have a single console that
users can log into and run a RT thread for audio but still not be able
to lock up the entire system. Right? So having an RT limit for this use
might actually be beneficial. But this is a very rare case, and if you
are the only one needing this type of feature, then it will likely not
make it into the kernel. But it if turns out that lots of people like
this feature, and want it, then it might have a chance, if there is no
other way to accomplish it.
Currently, it looks like you can use either Xen or just stick to one of
the patches you mentioned earlier.
-- Steve
next prev parent reply other threads:[~2006-07-17 13:59 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
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 [this message]
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=1153144753.652.12.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=Jean-Marc.Valin@USherbrooke.ca \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nielsen.esben@googlemail.com \
--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