Date: Mon, 06 Dec 2010 21:09:21 +0200 From: Andriy Gapon <avg@freebsd.org> To: Jung-uk Kim <jkim@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: non-invariant tsc and cputicker Message-ID: <4CFD34E1.40008@freebsd.org> In-Reply-To: <201012061401.17904.jkim@FreeBSD.org> References: <4CF92852.20705@freebsd.org> <201012061334.22475.jkim@FreeBSD.org> <4CFD2E1E.2080604@freebsd.org> <201012061401.17904.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CFD34E1.40008>