Date: Fri, 18 Jun 2021 22:32:34 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: John Baldwin <jhb@FreeBSD.org>, Warner Losh <imp@FreeBSD.org>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 4c0bc591466f - main - man9: add hz(9) and hardclock(9) Message-ID: <7c4c7acc-1fe4-28e4-4e1c-c08912eb0f99@grosbein.net> In-Reply-To: <10df4ab6-bee0-58f5-7d42-92850d526e01@FreeBSD.org> References: <202106181443.15IEhn4t010735@gitrepo.freebsd.org> <10df4ab6-bee0-58f5-7d42-92850d526e01@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
18.06.2021 22:18, John Baldwin wrote: > OTOH, it's > also true that there's no real reason for anything outside of the actual timer > code to use stathz (or even profhz) unlike 'hz' which is still used to set > timeout tick values. Not agreed: how do I get reliable per-CPU load stats in userland without sysctl kern.cp_times that exports incrementing raw "stathz-tick" counters? I need them to draw per-CPU graphs.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c4c7acc-1fe4-28e4-4e1c-c08912eb0f99>