From owner-freebsd-current@freebsd.org Sat Mar 6 02:53:48 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E4CD572052 for ; Sat, 6 Mar 2021 02:53:48 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dsq1R59KHz4dVj for ; Sat, 6 Mar 2021 02:53:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 1262s5wM059442; Fri, 5 Mar 2021 18:54:12 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Fri, 05 Mar 2021 18:54:05 -0800 From: Chris To: Yasuhiro Kimura Cc: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon In-Reply-To: <20210306.083323.1112779300812727243.yasu@utahime.org> References: <20210128.050242.1986722766748729591.yasu@utahime.org> <20210305.160311.867123118349124334.yasu@utahime.org> <20210306.083323.1112779300812727243.yasu@utahime.org> User-Agent: UDNSMS/17.0 Message-ID: <8a549830a3087998c1e2f80a5fb58199@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dsq1R59KHz4dVj X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2021 02:53:48 -0000 On 2021-03-05 15:33, Yasuhiro Kimura wrote: > From: Konstantin Belousov > 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. Not exactly what you're asking for. But sysctl sysctl(3) and loader(8) will provide some good clues. HTH --Chris > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"