From owner-freebsd-current@FreeBSD.ORG  Mon Dec  6 19:09:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B208F106566B;
	Mon,  6 Dec 2010 19:09:24 +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 C8AAE8FC12;
	Mon,  6 Dec 2010 19:09:23 +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 VAA14300;
	Mon, 06 Dec 2010 21:09:22 +0200 (EET) (envelope-from avg@freebsd.org)
Message-ID: <4CFD34E1.40008@freebsd.org>
Date: Mon, 06 Dec 2010 21:09:21 +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: Jung-uk Kim <jkim@freebsd.org>
References: <4CF92852.20705@freebsd.org> <201012061334.22475.jkim@FreeBSD.org>
	<4CFD2E1E.2080604@freebsd.org>
	<201012061401.17904.jkim@FreeBSD.org>
In-Reply-To: <201012061401.17904.jkim@FreeBSD.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: non-invariant tsc and cputicker
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 19:09:24 -0000

on 06/12/2010 21:01 Jung-uk Kim said the following:
> :-) Don't get me wrong, I generally agree with you *iff* it does not 
> hurt too much.  Anyway, this issue should be resolved from the root, 
> i.e., kern_resouce.c, if possible.

But what to resolve there?
I just want to always have a stable source "cpu ticks", and then everything else
should just work?

BTW, if someone comes up with a patch for more or less correct accounting when
"cpu ticks" frequency is allowed to change, then I am all for it.
But, IMO, it's just easier to use stable "cpu ticks".

-- 
Andriy Gapon