From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from hurricane.the-brannons.com (hurricane.the-brannons.com [IPv6:2602:ff06:725:1:20::25]) (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) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 291C61F953 for ; Wed, 21 Dec 2022 22:18:02 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=the-brannons.com header.i=@the-brannons.com header.b="Y1LZfDwx"; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=hurricane; bh=4xkfAlttqn 2Kp9ryciERkNadgyuM6usabgm/AJ2rmXo=; h=in-reply-to:date:references: subject:cc:to:from; d=the-brannons.com; b=Y1LZfDwxdd6TLizEMU8PW8tDHk12 zHKhxe5RMqeR8ma6FrRGn7wQtknPxZI7QtwA3uibA9jRgEXUKQwhMOo3c64eib2JTz43Kh 4784is/NGpZA5UE0qeNrq9f2mYmSLU2ONuZl9OVjSZBeTy6fmuhemBRonksKh/sm8jzi3X jg8= Received: by hurricane.the-brannons.com (OpenSMTPD) with ESMTPSA id f1a8ddeb (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) auth=yes user=chris; Wed, 21 Dec 2022 14:18:00 -0800 (PST) From: Chris Brannon To: Eric Wong Cc: meta@public-inbox.org Subject: Re: public-inbox-convert hangs on systems using musl libc References: <875ye5m1wo.fsf@the-brannons.com> <20221221122102.M600156@dcvr> <871qosna30.fsf@the-brannons.com> <20221221194855.GA5179@dcvr> <87mt7glc23.fsf@the-brannons.com> <20221221211114.M412849@dcvr> Autocrypt: addr=chris@the-brannons.com; prefer-encrypt=mutual; keydata= mDMEX37pCBYJKwYBBAHaRw8BAQdASkFrVm/MHGNpj7Oa+nq4b7eBg5LX5qnvS6ojH04ZE9+0LENo cmlzdG9waGVyIEJyYW5ub24gPGNocmlzQHRoZS1icmFubm9ucy5jb20+iJAEExYIADgWIQTFfzWT HzF7+QWPg09oJ1i8YNj4egUCX37pCAIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRBoJ1i8 YNj4esVsAQCJXDxhj5gZjcrNMmSH6Z+X5RDdbvsTRvS5wwQXM3g4kAEAjOrdx/fvZDiKL8dylDhU YUVVSkwWeOD2UtmYjm/QtwG4OARffukIEgorBgEEAZdVAQUBAQdAOMaQorDR8QUdM34/Q9mUyBvS 9WFK0Mb76dHyNkERx2kDAQgHiHgEGBYIACAWIQTFfzWTHzF7+QWPg09oJ1i8YNj4egUCX37pCAIb DAAKCRBoJ1i8YNj4eo/8AQC4AX6NMv65KQQU7s95T/1Y4E+Z7KTbvhKJeSjdDfj88AEA/qzPnDvl dLmqqNTqsfZCK81teOxSoNhRlhWcQ8QQ/wY= Date: Wed, 21 Dec 2022 14:17:59 -0800 In-Reply-To: <20221221211114.M412849@dcvr> (Eric Wong's message of "Wed, 21 Dec 2022 21:11:14 +0000") Message-ID: <87edssl7u0.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: Eric Wong writes: > The following changes MAX_INFLIGHT to 23 for all platforms (and > explains things better). I also wonder if you can find a > threshold for when things start failing (e.g. hardcoding 24 > should fail on FreeBSD) I did a binary search. On my Linux system with musl, deadlocks start at MAX_INFLIGHT >= 115. -- Chris