Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Nov 2002 20:32:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Nov 2002 20:32:48 -0500 Received: from 1-064.ctame701-1.telepar.net.br ([200.181.137.64]:14779 "EHLO 1-064.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Mon, 11 Nov 2002 20:32:47 -0500 Date: Mon, 11 Nov 2002 23:39:17 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: davidm@hpl.hp.com cc: Mario Smarduch , , Subject: Re: your mail In-Reply-To: <15824.915.758329.73126@napali.hpl.hp.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1316 Lines: 32 On Mon, 11 Nov 2002, David Mosberger wrote: > >>>>> On Mon, 11 Nov 2002 10:29:29 -0600, Mario Smarduch said: > > Mario> I know that on some commercial Unix systems there are ways to > Mario> cap the CPU utilization by user/group ids are there such > Mario> features/patches available on Linux? > The kernel patches available from this URL are pretty old (up to > 2.4.6, as far as I could see), and I'm not sure what the future plans > for PRM on Linux are. Perhaps someone else can provide more details. I'm (slowly) working on a per-user fair scheduler on top of Ingo's O(1) scheduler. Slowly because it's a fairly complex thing. Once that is done it should be possible to change the accounting to other resource containers and generally have fun assigning priorities, though that is beyond the scope of what I'm trying to achieve. cheers, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Current spamtrap: october@surriel.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/