Date: Mon, 10 Mar 2003 15:26:11 +0100 From: Marijn Meijles <marijn@bitpit.net> To: Vallo Kallaste <kalts@estpak.ee> Cc: arch@FreeBSD.org Subject: Re: New scheduler problem Message-ID: <20030310142610.GC7580@hoop.bitpit.net> In-Reply-To: <20030310080444.GB1122@kevad.internal> References: <20030206094040.GA2000@kevad.internal> <20030207211000.P72073-100000@mail.chesapeake.net> <20030210113928.GA10552@hoop.bitpit.net> <20030310041714.GA67308@terry.dragon2.net> <20030310080444.GB1122@kevad.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
Vallo Kallaste wrote: > On Mon, Mar 10, 2003 at 12:17:14PM +0800, Ying-Chieh Liao > <ijliao@FreeBSD.org> wrote: > > > On Mon, Feb 10, 2003 at 12:39:28 +0100, Marijn Meijles wrote: > > > With strict rescheduling turned on it runs a lot better. It is about as > > > responsive as the 4BSD scheduler. > > > > how to turn on "strict rescheduling" ? > > Can't remember the kernel configuration option, but IMO Jeff turned > it on by default some time ago, so you needn't be concerned about > it. Search arch@ archives for last month. It's turned on by default now. The latest version is quite good, although nice values are not handled correctly. But I believe Jeff is working on that. The same is true for forking. On a loaded system child processes are born with a rather high PRI value. -- Marijn@bitpit.net --- Hard work pays off later, laziness pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030310142610.GC7580>