From owner-freebsd-hackers Fri Jan 22 20:15:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09050 for freebsd-hackers-outgoing; Fri, 22 Jan 1999 20:15:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09045 for ; Fri, 22 Jan 1999 20:15:29 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 27760 invoked from network); 23 Jan 1999 04:15:12 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Jan 1999 04:15:12 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id XAA62055; Fri, 22 Jan 1999 23:15:10 -0500 (EST) Message-Id: <199901230415.XAA62055@y.dyson.net> Subject: Re: Error in vm_fault change In-Reply-To: <199901230331.UAA18297@psf.Pinyon.ORG> from "Russell L. Carter" at "Jan 22, 99 08:31:38 pm" To: rcarter@pinyon.org (Russell L. Carter) Date: Fri, 22 Jan 1999 23:15:10 -0500 (EST) Cc: dyson@iquest.net, dufault@hda.com, dillon@apollo.backplane.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Russell L. Carter said: > %> > %Your comments about "goals" are correct. The obsolete notion of priority > %is specious. > > No, it isn't. > > People (or rather organizations) are now using "OSS unix" stuff to > do things like control flight and targeting and other interesting > stuff. The lingo is based on "priority". Who gives a shit > about interactive users ;-). Meeting deadlines is probably > orthogonal to system throughput. > Deadlines are a major parameter. Even responsiveness to users is a form of deadline. Priority is only a short term scheduling hint, and doesn't really describe the resource requirements. Priority is a snapshot of what needs to run at an instant in time. Priority as a time invariant scalar (or even as the unix style slowly changing priority) isn't flexible enough anymore. Since we are talking here about resource mgmt, constraining ourselves to thinking about "priority" is just too inflexible. When looking into alternative scheduling mechanisms, priority just doesn't describe an adequate solution to the new range of problems (multimedia scheduling, realtime data, timesharing), that need to be solved concurrently (perhaps with the same resources.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message