From owner-freebsd-current@FreeBSD.ORG Tue Jun 5 01:17:26 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A815716A41F for ; Tue, 5 Jun 2007 01:17:26 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.freebsd.org (Postfix) with ESMTP id 659ED13C468 for ; Tue, 5 Jun 2007 01:17:26 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn02.u.washington.edu (hymn02.u.washington.edu [140.142.13.239]) by mxout1.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l551HPfo020049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 4 Jun 2007 18:17:26 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn02.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l551HP1n028455 for ; Mon, 4 Jun 2007 18:17:25 -0700 X-Auth-Received: from [134.134.136.3] by hymn02.u.washington.edu via HTTP; Mon, 04 Jun 2007 18:17:25 PDT Date: Mon, 4 Jun 2007 18:17:25 -0700 (PDT) From: youshi10@u.washington.edu To: current@freebsd.org In-Reply-To: <20070604170715.S606@10.0.0.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.4.175732 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Subject: Re: HEADS UP: threadlock going in, likely tonight. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 01:17:26 -0000 On Mon, 4 Jun 2007, Jeff Roberson wrote: > Ok folks, make sure you don't sup a snapshot from the middle of my commits > and you should have a solid working tree. > > I am going to work on the version of ule with per-cpu locks (sched_smp) a > little while longer before sending that out again. I suspect this will address > many of the scheduling related complaints and performance problems people have > had. > > Thanks, > Jeff > > On Mon, 4 Jun 2007, Jeff Roberson wrote: > >> I will now begin committing threadlock. >> >> Please wait to cvsup until I send another mail. >> >> Thanks, >> Jeff >> >> On Mon, 4 Jun 2007, Jeff Roberson wrote: >> >>> This has been up for review and testing for some time. I think it's ready >>> for prime-time. Only one new bug came up over the weekend and I believe I >>> have that fixed. >>> >>> I'm going to commit the patch in stages but the tree will not be >>> functional in between. I'm not able to break it down into several >>> functional steps but I want to leave meaningful commit messages in several >>> files. >>> >>> I will send out one more mail when I start and another when I'm done. >>> >>> Thanks, >>> Jeff Jeff, Thanks again and I'll be sure to burn in the new scheduling prio system on my desktop :). Cheers, -Garrett