From owner-freebsd-current@freebsd.org Mon Mar 29 06:28:03 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 53B7F5BDC14 for ; Mon, 29 Mar 2021 06:28:03 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F82h20Lv9z4fk1 for ; Mon, 29 Mar 2021 06:28:01 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4F82gz5nm1z6dSH; Mon, 29 Mar 2021 08:27:59 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id bKJZCJEx_vVR; Mon, 29 Mar 2021 08:27:57 +0200 (CEST) Subject: Re: 13.0 RC4 might be delayed To: Greg Rivers , FreeBSD Current Cc: Graham Perrin , David G Lawrence References: <2766233C-3CC7-4B02-95AB-7555A60FFD81@samsco.org> <1b3605eb-388e-283b-d907-67058ea62c0a@madpilot.net> <20210329013713.GA52047@mailx.dglawrence.com> <3765721.kAAoriTUSa@no.place.like.home> From: Guido Falsi Message-ID: <7c952519-d82e-c6c3-19c1-908a89defce0@madpilot.net> Date: Mon, 29 Mar 2021 08:27:56 +0200 In-Reply-To: <3765721.kAAoriTUSa@no.place.like.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F82h20Lv9z4fk1 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.50 / 15.00]; MISSING_MIME_VERSION(2.00)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[159.69.1.99:from]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[freebsd-current]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[159.69.1.99:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_CC(0.00)[gmail.com,dglawrence.com]; MAILMAN_DEST(0.00)[freebsd-current]; SUSPICIOUS_RECIPS(1.50)[] 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: Mon, 29 Mar 2021 06:28:03 -0000 On 29/03/21 06:26, Greg Rivers wrote: > On Sunday, 28 March 2021 20:37:13 CDT David G Lawrence via freebsd-current wrote: >>>> On 27/03/21 06:04, David G Lawrence via freebsd-current wrote: >>>>>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin >>>>>> wrote: >>>>>> >>>>>>> On 26/03/2021 03:40, The Doctor via freebsd-current wrote: >>>>>>>> ??? if people are having issues with ports like ??? >>>>>>> >>>>>>> If I'm not mistaken: >>>>>>> >>>>>>> * 13.0-RC3 seems to be troublesome, as a guest machine, with >>>>>>> emulators/virtualbox-ose 6.1.18 as the host >>>>>>> >>>>>>> * no such trouble with 12.0-RELEASE-p5 as a guest. >>>>>>> >>>>>>> I hope to refine the bug report this weekend. >>>>>>> >>>>>> >>>>>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. >>>>>> That >>>>>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and >>>>>> will try again shortly to see if it's any better. >>>>> >>>>> Kevin, >>>>> >>>>> ?????? Make sure you have these options in your /etc/sysctl.conf : >>>>> >>>>> vfs.aio.max_buf_aio=8192 >>>>> vfs.aio.max_aio_queue_per_proc=65536 >>>>> vfs.aio.max_aio_per_proc=8192 >>>>> vfs.aio.max_aio_queue=65536 >>>>> >>>>> ?????? ...otherwise the guest I/O will random hang in VirtualBox. This >>>>> issue was >>>>> mitigated in a late 5.x VirtualBox by patching to not use AIO, but the >>>>> issue >>>>> came back in 6.x when that patch wasn't carried forward. >>>> >>>> Sorry I lost that patch. Can you point me to the patch? Maybe it can be >>>> easily ported. >>>> >>> >>> I found the relevant commit. Please give me some time for testing and >>> I'll put this patch back in the tree. >> >> If you're going to put that patch back in, then AIO should probably be >> made an option in the port config, as shutting AIO off by default will >> have a significant performance impact. Without AIO, all guest IO will >> be become synchronous. >> Ideally, someone would fix the AIO case by either increasing the defaults >> in FreeBSD to something reasonable, and/or properly handing the case when >> an AIO limit is reached. >> > Agreed, it would be a shame to have AIO disabled by default. A one time update to sysctl.conf (per the existing pkg message!) is a small price to pay for much better performance. > Good point. Now the question is, what the default should be. Since the correct aio configuration is in the pkg-message and easy to setup I'd go for default to AIO turned on. I Have a few things on he pope with ports, I will need some days to work this out. -- Guido Falsi