linux-kernel - Re: per-thread rusage

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:	Tue, 1 May 2007 15:34:40 -0700
From:	Bill Irwin <bill.irwin@...cle.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Ulrich Drepper <drepper@...il.com>,
	Bill Irwin <bill.irwin@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Eric Dumazet <dada1@...mosbay.com>,
	linux-kernel@...r.kernel.org, wli@...omorphy.com
Subject: Re: per-thread rusage

On Tue, May 01, 2007 at 06:27:24PM -0400, Theodore Tso wrote:
> 	There are two ways of implementing this.  One is to have the
> JVM periodically poll using a pthread_getrusage() interface.  A better
> choice might be some kind of per-thread CPU limit, that would result
> in a thread-specific SIGXCPU signal.  But there are no interfaces
> today that do anything like this.
> 	Do you have any thoughts or preferences about how this might
> be done, if we tried to about doing something like a per-thread
> SIGXCPU functionality?  If not, pthread_getrusage() might be
> sufficient, if not the most efficient way of doing things.

I just so happen to think we should implement a variety of CPU resource
limits beyond what we now do, so this, too, interests me.


-- wli
-
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/