Date: Sat, 06 Mar 2021 08:33:23 +0900 (JST) From: Yasuhiro Kimura <yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon Message-ID: <20210306.083323.1112779300812727243.yasu@utahime.org> In-Reply-To: <YEKYDlPuvn6TL4xs@kib.kiev.ua> References: <20210128.050242.1986722766748729591.yasu@utahime.org> <20210305.160311.867123118349124334.yasu@utahime.org> <YEKYDlPuvn6TL4xs@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Konstantin Belousov <kostikbel@gmail.com> Subject: Re: Waiting for bufdaemon Date: Fri, 5 Mar 2021 22:43:58 +0200 > My belief is that this commit helps more users than it hurts. Namely, > the VMWare and KVM users, which are majority, use fast timecounter, > comparing to the more niche hypervisors like VirtualBox. > > For you, a simple but manual workaround, setting the timecounter to > ACPI (?) or might be HPET, with a loader tunable, should do it. Then please let me know the name of it. I have experienced same situation several time. That is, I faced a problem and asked for it on ML. Then I was told to try some tunable. So I thought there may be tunable that can be used as workaround in this case. But for those who isn't familiar with kernel internal, it it quite hard to find it without knowing its name. If all tunable were listed with brief explanation in one document, then I saw it and could pick up possible candidates. But actually they are documented separately among many man pages. So the first difficulty is to find man page in which possible tunable may be explained. If the problem is releted to some device, it is most hopeful to check its man page. But in this case, even after reading the commit message, I had no idea which man page to check. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210306.083323.1112779300812727243.yasu>