From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:10:34 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7987F106566C; Mon, 6 Dec 2010 18:10:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1B88FC15; Mon, 6 Dec 2010 18:10:34 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id oB6IAY47038768; Mon, 6 Dec 2010 10:10:34 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id oB6IAXtk038767; Mon, 6 Dec 2010 10:10:33 -0800 (PST) (envelope-from sgk) Date: Mon, 6 Dec 2010 10:10:33 -0800 From: Steve Kargl To: Kostik Belousov Message-ID: <20101206181033.GA38739@troutmask.apl.washington.edu> References: <20101205231829.GA68156@troutmask.apl.washington.edu> <201012060944.03196.jhb@freebsd.org> <20101206163830.GA53157@troutmask.apl.washington.edu> <20101206173531.GI2417@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101206173531.GI2417@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Process accounting/timing has broken recently 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: Mon, 06 Dec 2010 18:10:34 -0000 On Mon, Dec 06, 2010 at 07:35:31PM +0200, Kostik Belousov wrote: > On Mon, Dec 06, 2010 at 08:38:30AM -0800, Steve Kargl wrote: > > John, > > > > Thanks for the comment. It seems this splitting has become > > worse (for some definition of worse) in that previously the > > user time variation was on the order of tenth of a second not > > seconds. In thinking about the issue, I recalled that some > > changes to npx.c were committed 10 days ago. Perhaps, there > > is slightly more context switch overhead in dealing with the > > FPU registers, and this has increased the sys time. > If you can confirm this statement, it would be interesting. Otherwise, > I claim that the changes did not affected the context switch path at > all. The changes were mostly relevant for context(2) family of functions > and debugger access to the FPU register file. I won't be able to test this possibiolity until later tonight (about 9 hours from now). -- Steve