From owner-freebsd-current@FreeBSD.ORG Thu Mar 23 20:35:40 2006 Return-Path: X-Original-To: current@FreeBSD.ORG 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 546F916A420 for ; Thu, 23 Mar 2006 20:35:40 +0000 (UTC) (envelope-from sobomax@FreeBSD.ORG) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594FC43D49 for ; Thu, 23 Mar 2006 20:35:38 +0000 (GMT) (envelope-from sobomax@FreeBSD.ORG) Received: from [192.168.1.46] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.4/8.13.4) with ESMTP id k2NKlQ9a003668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Mar 2006 12:47:34 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <44230682.4010500@FreeBSD.org> Date: Thu, 23 Mar 2006 12:35:14 -0800 From: Maxim Sobolev User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Scott Long References: <20060322122906.A41691@xorpc.icir.org> <20060323001555.GA1811@tin.it> <20060323142518.GA1308@tin.it> <20060323063139.A67037@xorpc.icir.org> <4422B3C8.3080303@samsco.org> <20060323064805.B67264@xorpc.icir.org> <4422B5A5.8040006@samsco.org> In-Reply-To: <4422B5A5.8040006@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: interesting(?) data on network interrupt servicing 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: Thu, 23 Mar 2006 20:35:40 -0000 Scott Long wrote: > Luigi Rizzo wrote: >> On Thu, Mar 23, 2006 at 07:42:16AM -0700, Scott Long wrote: >> >>> Luigi Rizzo wrote: >>> >>>> On Thu, Mar 23, 2006 at 03:25:18PM +0100, Paolo Pisati wrote: >> >> ... >> >>>>> ok, i updated my CURRENT and rerun the tests (and while here i >>>>> disabled SMP): >>>>> >>>>> phk's optimization to cpu ticks calculation shaved 4k ticks, >>>> >>>> this makes it a very good candidate for MFC when 6.1 is out ? >> >> ... >> >>> I haven't been paying close enough attention, have all of the calcru >>> problems and other side effects been fixed from phk's work? >> >> >> we should ask phk. As far as i remember the only "problem" >> is/was that the sys/user times are computed as if the >> cpu were running at its max speed. But this is in fact >> a good thing because it is a more consistent measurement of >> the cost of the CPU work, which decouples us from having >> to take care of variable cpu speed. >> >> luigi > > No, I'm talking about all of the resulting problems with processes > generating calcru messages on the console. I still see them here with ACPI-safe TC. -Maxim