From owner-freebsd-hackers  Mon Dec  8 17:06:51 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA07463
          for hackers-outgoing; Mon, 8 Dec 1997 17:06:51 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA07438
          for <freebsd-hackers@freebsd.org>; Mon, 8 Dec 1997 17:06:45 -0800 (PST)
          (envelope-from tlambert@usr01.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id SAA23266;
	Mon, 8 Dec 1997 18:18:22 -0700 (MST)
Received: from usr01.primenet.com(206.165.6.201)
 via SMTP by smtp02.primenet.com, id smtpd023234; Mon Dec  8 18:18:13 1997
Received: (from tlambert@localhost)
	by usr01.primenet.com (8.8.5/8.8.5) id SAA24889;
	Mon, 8 Dec 1997 18:05:59 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199712090105.SAA24889@usr01.primenet.com>
Subject: Re: Process scheduling: nice does not work ???
To: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis)
Date: Tue, 9 Dec 1997 01:05:59 +0000 (GMT)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199712082219.UAA13229@gaia.coppe.ufrj.br> from "Joao Carlos Mendes Luis" at Dec 8, 97 08:19:31 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>   I've been doing some test with cpu-intensive scheduling in FreeBSD
> 2.2-stable, when I found what seems to be an error in the scheduler.


Standard UNIX priorities work like this:

				prio	20	19	18	17	...
					^	^	^	^
IF something here run it ---------------'	|	|	|
ELSE IF something here run it ------------------'	|	|
ELSE IF something here run it --------------------------'	|
ELSE IF something here run it ----------------------------------'
...

Note: these are base priorities, which the system will adjust based on
I/O vs. CPU utilization.


Your processes must have both been I/O bound.

FreeBSD is doing what it's supposed to.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.