From owner-freebsd-current Mon Feb 10 17:40:44 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 8321437B401; Mon, 10 Feb 2003 17:40:43 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3AA343FE3; Mon, 10 Feb 2003 17:40:42 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h1B1aoA92532; Mon, 10 Feb 2003 20:36:50 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 10 Feb 2003 20:36:50 -0500 (EST) From: Jeff Roberson To: Kris Kennaway Cc: jeff@FreeBSD.ORG, Subject: Re: Still problems with ULE In-Reply-To: <20030211010545.GA25714@rot13.obsecurity.org> Message-ID: <20030210202759.Y23474-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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 think I know what the remaining problems are. I'll make a post on current@ when they're all sorted out. Thanks for testing! Cheers, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message