From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 03:48:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC06037B401 for ; Wed, 2 Apr 2003 03:48:53 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E33543F93 for ; Wed, 2 Apr 2003 03:48:52 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA29312; Wed, 2 Apr 2003 21:48:38 +1000 Date: Wed, 2 Apr 2003 21:48:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Sheldon Hearn In-Reply-To: <20030402091300.GG725@starjuice.net> Message-ID: <20030402212503.N26453@gamplex.bde.org> References: <20030402015226.E64602-100000@mail.chesapeake.net> <20030402091300.GG725@starjuice.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 11:48:54 -0000 On Wed, 2 Apr 2003, Sheldon Hearn wrote: > On (2003/04/02 01:54), Jeff Roberson wrote: > > > It probably still needs some tweaking but it seems to be MUCH better now. > > New algorithm entirely. > > > > nice +20 processes will not run if anything else wants to. > > Some of us have been waiting for that behaviour for a long time (long > before you started working on ULE). Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8, so you shouldn't have waited more than negative 4 years for it :-). The strict implementation of this behaviour in these releases causes priority inversion problems, but the problems apparently aren't very important. The scaling of niceness was re-broken in -current about 3 years ago to "fix" the priority inversion problems. This is with SCHED_4BSD. SCHED_ULE has larger problems. Bruce