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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070502000458.2a7885d9@the-village.bc.nu>
Date:	Wed, 2 May 2007 00:04:58 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Bill Irwin <bill.irwin@...cle.com>
Cc:	Theodore Tso <tytso@....edu>, 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

> 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.

Agreed - and make them all 64bit while doing the cleanup. One thing
several Unixen have we don't for 32bi boxes is a proper set of 64bit
resource handling for memory/file etc.

We could also start using the CPU facilities to enforce some of
the really interesting real time process ones (like main memory
bandwidth) that at the moment we have no control over and can lead to
very unfair behaviour.

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