From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031289AbXDQXLJ (ORCPT ); Tue, 17 Apr 2007 19:11:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030930AbXDQXLJ (ORCPT ); Tue, 17 Apr 2007 19:11:09 -0400 Received: from waste.org ([66.93.16.53]:35163 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031291AbXDQXLH (ORCPT ); Tue, 17 Apr 2007 19:11:07 -0400 Date: Tue, 17 Apr 2007 17:57:23 -0500 From: Matt Mackall To: William Lee Irwin III Cc: Ingo Molnar , Davide Libenzi , Nick Piggin , Peter Williams , Mike Galbraith , Con Kolivas , ck list , Bill Huey , Linux Kernel Mailing List , Linus Torvalds , Andrew Morton , Arjan van de Ven , Thomas Gleixner Subject: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] Message-ID: <20070417225723.GP11115@waste.org> References: <20070417061503.GC1057@wotan.suse.de> <20070417070949.GR8915@holomorphy.com> <20070417073308.GB30559@elte.hu> <20070417090538.GU8915@holomorphy.com> <20070417092422.GA19414@elte.hu> <20070417220809.GF11166@waste.org> <20070417223256.GP2986@holomorphy.com> <20070417223909.GO11115@waste.org> <20070417225902.GQ2986@holomorphy.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070417225902.GQ2986@holomorphy.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2007 at 03:59:02PM -0700, William Lee Irwin III wrote: > On Tue, Apr 17, 2007 at 03:32:56PM -0700, William Lee Irwin III wrote: > >> I'm already working with this as my assumed nice semantics (actually > >> something with a specific exponential base, suggested in other emails) > >> until others start saying they want something different and agree. > > On Tue, Apr 17, 2007 at 05:39:09PM -0500, Matt Mackall wrote: > > Good. This has a couple nice mathematical properties, including > > "bounded unfairness" which I mentioned earlier. What base are you > > looking at? > > I'm working with the following suggestion: > > > On Tue, Apr 17, 2007 at 09:07:49AM -0400, James Bruce wrote: > > Nonlinear is a must IMO. I would suggest X = exp(ln(10)/10) ~= 1.2589 > > That value has the property that a nice=10 task gets 1/10th the cpu of a > > nice=0 task, and a nice=20 task gets 1/100 of nice=0. I think that > > would be fairly easy to explain to admins and users so that they can > > know what to expect from nicing tasks. > > I'm not likely to write the testcase until this upcoming weekend, though. So that means there's a 10000:1 ratio between nice 20 and nice -19. In that sort of dynamic range, you're likely to have non-trivial numerical accuracy issues in integer/fixed-point math. (Especially if your clock is jiffies-scale, which a significant number of machines will continue to be.) I really think if we want to have vastly different ratios, we probably want to be looking at BATCH and RT scheduling classes instead. -- Mathematics is the supreme nostalgia of our time.