From owner-freebsd-stable@FreeBSD.ORG Tue Feb 8 12:43:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41D1E16A4E7 for ; Tue, 8 Feb 2005 12:43:06 +0000 (GMT) Received: from mailgw.icon.bg (mailgw.icon.bg [213.222.48.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4710A43D46 for ; Tue, 8 Feb 2005 12:43:05 +0000 (GMT) (envelope-from v0rbiz@icon.bg) Received: from localhost ([::1] helo=mailgw.icon.bg) by mailgw.icon.bg with esmtp (Exim 4.43 (FreeBSD)) id 1CyUk1-0009AY-Cl for freebsd-stable@freebsd.org; Tue, 08 Feb 2005 14:45:22 +0200 Received: from 213.222.48.10 (SquirrelMail authenticated user v0rbiz1) by mailgw.icon.bg with HTTP; Tue, 8 Feb 2005 14:45:17 +0200 (EET) Message-ID: <4253.213.222.48.10.1107866717.squirrel@mailgw.icon.bg> In-Reply-To: <200502081333.08964.michaelnottebrock@gmx.net> References: <200502081333.08964.michaelnottebrock@gmx.net> Date: Tue, 8 Feb 2005 14:45:17 +0200 (EET) From: "Viktor Ivanov" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=windows-1251 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -2.8 (--) Subject: Re: ULE status X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: v0rbiz@icon.bg List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 12:43:06 -0000 On Tue, Февруари 8, 2005 14:33, Michael Nottebrock каза: > On Tuesday, 8. February 2005 13:07, Mipam wrote: >> I saw several changes to sched_ule.c in the 5 stable branch. >> Beneath is one of them: >> >> http://lists.freebsd.org/pipermail/cvs-src/2005-February/039863.html >> >> Is the ULE scheduler still far from stable in RELENG_5 or not? > > You can now compile a kernel with options SCHED_ULE again. How well it > works > is for yourself to determine :-) (I've been using it on my UP machine here > since yesterday only). Hi there I've been using only SCHED_ULE on my UP WS, even when there was #error def. It never broke, not even once :) Though I think there's trouble with SMP and/or HTT. I tried it once on a P4 and it paniced. On the other hand, using SCHED_ULE improves sound quality and general system 'response' concerning GUI... don't know 'bout performance. Regards