Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264993AbTGGOkV (ORCPT ); Mon, 7 Jul 2003 10:40:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265006AbTGGOkV (ORCPT ); Mon, 7 Jul 2003 10:40:21 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:12185 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S264993AbTGGOkT (ORCPT ); Mon, 7 Jul 2003 10:40:19 -0400 X-AuthUser: davidel@xmailserver.org Date: Mon, 7 Jul 2003 07:47:14 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mcafeelabs.com To: Mel Gorman cc: Daniel Phillips , Jamie Lokier , Andrew Morton , Linux Kernel Mailing List , Linux Memory Management List Subject: Re: 2.5.74-mm1 In-Reply-To: Message-ID: References: <20030703023714.55d13934.akpm@osdl.org> <200307060414.34827.phillips@arcor.de> <200307071424.06393.phillips@arcor.de> 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: 1045 Lines: 28 On Mon, 7 Jul 2003, Mel Gorman wrote: > On Mon, 7 Jul 2003, Daniel Phillips wrote: > > > And set up distros to grant it by default. Yes. > > > > The problem I see is that it lets user space priorities invade the range of > > priorities used by root processes. > > That is the main drawback all right but it could be addressed by having a > CAP_SYS_USERNICE capability which allows a user to renice only their own > processes to a highest priority of -5, or some other reasonable value > that wouldn't interfere with root processes. This capability would only be > for applications like music players which need to give hints to the > scheduler. The scheduler has to work w/out external input, period. If it doesn't we have to fix it and not to force the user to submit external hints. - Davide - 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/