From owner-freebsd-hackers@FreeBSD.ORG  Fri Nov 19 16:57:44 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 248CD106564A;
	Fri, 19 Nov 2010 16:57:44 +0000 (UTC) (envelope-from avg@freebsd.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 0F87E8FC16;
	Fri, 19 Nov 2010 16:57:42 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA16273;
	Fri, 19 Nov 2010 18:57:41 +0200 (EET) (envelope-from avg@freebsd.org)
Message-ID: <4CE6AC85.9040802@freebsd.org>
Date: Fri, 19 Nov 2010 18:57:41 +0200
From: Andriy Gapon <avg@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org, Alexander Motin <mav@freebsd.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 
Subject: statclock(n)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 16:57:44 -0000


Alexander,

I wonder if instead of calling statclock() multiple times (after an idle period)
we couldn't call it just with an appropriate N parameter.
So some stats like e.g. cp_time[] could do +=N instead of ++.
Other stats ru_ixrss need to be updated only once.
Similarly, N could be passed further down to sched_clock() and handled there too.

-- 
Andriy Gapon