From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 457EACA9ED0 for ; Mon, 4 Nov 2019 03:04:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1624C21929 for ; Mon, 4 Nov 2019 03:04:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="Pu1X0tV2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729065AbfKDDE1 (ORCPT ); Sun, 3 Nov 2019 22:04:27 -0500 Received: from terminus.zytor.com ([198.137.202.136]:53415 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728643AbfKDDE0 (ORCPT ); Sun, 3 Nov 2019 22:04:26 -0500 Received: from [IPv6:2601:646:8600:3281:102f:ba8b:7a69:7a8a] ([IPv6:2601:646:8600:3281:102f:ba8b:7a69:7a8a]) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id xA433haZ092262 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 3 Nov 2019 19:03:45 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com xA433haZ092262 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2019091901; t=1572836630; bh=YHmnDJJIhxFAT6Io1jUZZxs7VOrc7D7NbUvhYDnhU24=; h=Date:In-Reply-To:References:Subject:To:CC:From:From; b=Pu1X0tV2m5PAlzR/appMLa4FxmBFAkI+Mg0Od1AwSIr5NVB4+aYSg7fyKLIt4/Uri f0xZHC3iKXV0iY8Z6aIb7iJmBy4ynHBtCFR5xpFmKVcpj+MKO5miwu/YLUDxiBXqfI TF+KTLwq5faYWD1ktGqsSZimovkkpjXcgK8I9x5S4CgkTjGdZm21OexRzfyjjVrwvS 5WSYk2tQaPR027iDhUMUR/qpfDcNc7HDm8R2JiyZnhaem1NCYGyT69ITqEcniMKd3f crkNBnlimcxjKGUaizj+MBCCQqvlQr339xzpYq4HIQfUIiR5cR3/wbRlezlUI0X4LA YCFeDbrSUVg1A== Date: Sun, 03 Nov 2019 19:03:36 -0800 User-Agent: K-9 Mail for Android In-Reply-To: References: <20190620062246.2665-1-e5ten.arch@gmail.com> <20191029210250.17007-1-e5ten.arch@gmail.com> <40DC5B42-6C0D-4A5B-B23E-884ADB0108F0@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v3] replace timeconst bc script with an sh script To: Ethan Sommer CC: Jonathan Corbet , Federico Vaga , "Chang S. Bae" , Andrew Morton , Arnd Bergmann , Masahiro Yamada , Kieran Bingham , Ingo Molnar , Borislav Petkov , Mark Rutland , John Stultz , Kees Cook , Corey Minyard , Thomas Gleixner , linux-doc@vger.kernel.org, Linux Kernel Mailing List From: hpa@zytor.com Message-ID: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On November 3, 2019 3:57:06 PM PST, Ethan Sommer = wrote: >> The point isn't to make it work *now*, but getting it to *stay* work=2E >Since the only thing that can change to affect the outcome of the >script >or program is the value of CONFIG_HZ, isn't knowing that it works >within >a range of any reasonable values to set CONFIG_HZ to enough to know >that >it will stay working? I just tested again using the bc script and my C >program, and this time I tested every possible value up to 100000, and >they both still matched output=2E It doesn't seem like there's something >that would cause the C program to stop working in the future due to >precision issues=2E No, it's not=2E Because some time we are going to want to change the way t= he constants we need, or use them for something else, and be so on=2E --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E