From owner-freebsd-current Mon Feb 10 18:58:41 2003 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 076BD37B401 for ; Mon, 10 Feb 2003 18:58:40 -0800 (PST) Received: from opiate.thirteenandtwo.org (CPE0030ab0ef2bb-CM014490123332.cpe.net.cable.rogers.com [24.103.202.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1644243F93 for ; Mon, 10 Feb 2003 18:58:37 -0800 (PST) (envelope-from munish@opiate.thirteenandtwo.org) Received: by opiate.thirteenandtwo.org (Postfix, from userid 1001) id 2BD2887; Mon, 10 Feb 2003 21:58:36 -0500 (EST) Date: Mon, 10 Feb 2003 21:58:36 -0500 From: Munish Chopra To: current@FreeBSD.ORG Subject: Re: Still problems with ULE Message-ID: <20030211025836.GA616@opiate.thirteenandtwo.org> Mail-Followup-To: current@FreeBSD.ORG References: <20030211010545.GA25714@rot13.obsecurity.org> <20030210202759.Y23474-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030210202759.Y23474-100000@mail.chesapeake.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2003-02-10 20:36 +0000, Jeff Roberson wrote: > On Mon, 10 Feb 2003, Kris Kennaway wrote: > > > I gave ULE another try just now, following your recent commits, and > > I'm seeing even worse problems: > > > > At boot time when the X server is loading, disk activity occurs > > briefly about once every 2 seconds; the mouse is active briefly at the > > same time, and nothing much else happens for about a minute until the > > entire system deadlocks. > > Very weird. Is this on UP or SMP? I'm still working on a couple of > issues with ule. I think I am very happy with the dynamic priority > selection now but in the process the slice size selection got kinda dirty. > Its pretty much bug for bug compatible with the old scheduler's context > switching decisions but the errors there are more serious with this > design. I also think the max slice size is way too high now. I was > experimenting with that and I accidentally checked it in. > I'm seeing some of the same with sources from about 90 minutes ago. UP system, loading X is a pain. Interactivity is somewhat alright up until I start a compile, at which point the system goes down on it's knees. It hasn't completely deadlocked (yet?), but it's pretty much unusable if anything intensive is happening. -- Munish Chopra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message