From owner-freebsd-stable@FreeBSD.ORG Fri Dec 23 00:35:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id F35B21065673; Fri, 23 Dec 2011 00:35:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 385D4157E19; Fri, 23 Dec 2011 00:35:08 +0000 (UTC) Message-ID: <4EF3CCBB.6060503@FreeBSD.org> Date: Thu, 22 Dec 2011 16:35:07 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111110 Thunderbird/8.0 MIME-Version: 1.0 To: Adrian Chadd References: <4EE1EAFE.3070408@m5p.com> <20111215215554.GA87606@troutmask.apl.washington.edu> <20111222005250.GA23115@troutmask.apl.washington.edu> <20111222103145.GA42457@onelab2.iet.unipi.it> <20111222184531.GA36084@troutmask.apl.washington.edu> <4EF37E7B.4020505@FreeBSD.org> <20111222194740.GA36796@troutmask.apl.washington.edu> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Andriy Gapon , Steve Kargl Subject: Re: SCHED_ULE should not be the default X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 00:35:53 -0000 On 12/22/2011 16:23, Adrian Chadd wrote: > You've done something > that noone else has actually done - provided actual results from > real-life testing, rather than a hundred posts of "I remember seeing > X, so I don't use ULE." Not to take away from Steve's excellent work on this, but I actually spent weeks following detailed instructions from various people using ktr, dtrace, etc. and was never able to produce any data that helped point anyone to something that could be fixed. I'm pretty sure that others have tried as well. That said, I'm glad that Steve was able to produce useful results, and hopefully it will lead to improvements. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/