lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 17 Jul 2006 09:59:13 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jean-Marc Valin <Jean-Marc.Valin@...erbrooke.ca>
Cc:	Esben Nielsen <nielsen.esben@...glemail.com>,
	Lee Revell <rlrevell@...-job.com>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: Where is RLIMIT_RT_CPU?

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ