From owner-freebsd-current Sun Jun 11 3: 6:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from oznet15.ozemail.com.au (oznet15.ozemail.com.au [203.2.192.116]) by hub.freebsd.org (Postfix) with ESMTP id 247ED37B557; Sun, 11 Jun 2000 03:06:00 -0700 (PDT) (envelope-from obituary@ozemail.com.au) Received: from carcass.au.hartware.com (slnew51p44.ozemail.com.au [203.108.150.60]) by oznet15.ozemail.com.au (8.9.0/8.6.12) with ESMTP id UAA15030; Sun, 11 Jun 2000 20:05:54 +1000 (EST) Received: (from obituary@localhost) by carcass.au.hartware.com (8.9.3/8.9.3) id UAA00283; Sun, 11 Jun 2000 20:03:22 +1000 (EST) (envelope-from obituary) Date: Sun, 11 Jun 2000 20:03:22 +1000 From: "Jacob A. Hart" To: Brian Fundakowski Feldman Cc: Doug Barton , Sheldon Hearn , FreeBSD-CURRENT Subject: Re: Scheduler changes? Message-ID: <20000611200322.A236@carcass.au.hartware.com> References: <20000528135331.A241@carcass.au.hartware.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from green@FreeBSD.ORG on Fri, Jun 09, 2000 at 08:28:06PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 09, 2000 at 08:28:06PM -0400, Brian Fundakowski Feldman wrote: > > The diff should make a process at -20 which uses all available CPU > schedule just slightly the ahead of a process at +20 which uses no CPU. > A process which uses full CPU at 0 niceness would have a priority of > 128, whereas a process using no CPU at 0 niceness would have a priority > of 90. All processes will always have a priority less than or equal to > 128, which is the priority at which a process with a niceness of +20 > always runs at. A +20 process won't get better priority than anything > else, period. Try it out, see how it works for you:) I tried this patch today. While it didn't quite fix the problem, it sure made for some interesting pacman gameplay. ;-) Using idprio as Volodymyr suggested seems to be a viable workaround. You mentioned in another message that idprio could potentially deadlock my machine, though. Under what conditions could this happen (and how likely is it to occur)?=20 -jake --=20 Jacob A. Hart Powered by: FreeBSD 5.0-CURRENT #18: Sun Jun 11 19:25:03 EST 2000 --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: xaekhSYZnG9LAfRSXDDkSOwarV+x2Exf iQA/AwUBOUNj6X1KIGEEZDODEQIeFgCeMbEXHrRISy5op+8yVVxN2Pd+cVUAoNba 4naBdYE4w7oImABKD9RLNTOe =uYGv -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message