Received: by 2002:a05:7412:a9a2:b0:e2:908c:2ebd with SMTP id o34csp2855801rdh; Mon, 30 Oct 2023 09:32:03 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGXAleYeLgoxffPm94gl74NiUyFTJS76tziQpNuMj7YNL5Gokmj7745+z6S0b9GFV4Q6hX8 X-Received: by 2002:a17:90a:fd01:b0:27f:ebfa:1112 with SMTP id cv1-20020a17090afd0100b0027febfa1112mr7137162pjb.5.1698683523394; Mon, 30 Oct 2023 09:32:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698683523; cv=none; d=google.com; s=arc-20160816; b=R+xWbZGsLVUIq0Z3lzbZQBKbOW1YRCqe7WJ+nh7wHdGMnioed913FL+WXfnP/XEZ3N kIh8jlWL/bOC1MrkzjPDl6zQA2M3dgKwOLc3Yjz9fDAiHTs6B8gJKo2xwB/Qqk5TacqC n2m2+lqbole3mG81vHJmhGXoYkzH+nd+HGS8II5PjogO9B2rhk8TfFrMSkKZXFB6WZKl coueNXu/K0cnBl/YhCtsc3Ry6O1xpk3hcJAMHbWNz2byQNpfQpK4X6baoDJKLuSjqLqW TaBjgCHSYS7jsq32ldT+uGXasgBhFC5asACG81Yt1Ijv0+qBz5d7j09waeKpbOC5nkUd FrGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:subject:user-agent:mime-version:date:message-id; bh=/XLIe5sPtZ0ue2D1v7ZkqSMmwR1fsYiEU3ykiiRI2SM=; fh=4A1c5sqIOwHhOdbKPyH87xHwZAjvyMjO3B9A+L03njQ=; b=ExxpLGkF5vHMh9GoD7OuKj8lNTFR/rSB9QQ8D67vLxWhRu2Nw9xhOE+Oyw87Kp9yG4 0XYb2kBFZWfNrvYNm8PynyKk3SjJbmgXlNTY4JsFf+5Jmn9hUp1/Pb5CUuPCRiiLxb8D +KgxZKhVdkAFc7EhTlW7Q3zH9uRTnaseNjFARuZJg26EG1dIfvKltscMUl1YHLEf9LdK FfaZXIAeV3EIvT/8V/476+z4EbZtWoXlgp0mnCn3eYYix9l6kubX2icOquG2uCDtWj53 TZhkdmNKnC/AI+PrNyA8TPn/ERr4rpvDuR0u51VNJJNaVDHAF0QEvNPJCk9FuN+iN6VU XINw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lipwig.vger.email (lipwig.vger.email. [2620:137:e000::3:3]) by mx.google.com with ESMTPS id i20-20020a17090adc1400b002791b907f0csi2755687pjv.121.2023.10.30.09.31.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Oct 2023 09:32:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id F229980AD125; Mon, 30 Oct 2023 09:31:43 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233878AbjJ3Qbg (ORCPT + 99 others); Mon, 30 Oct 2023 12:31:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38910 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233885AbjJ3Qbe (ORCPT ); Mon, 30 Oct 2023 12:31:34 -0400 X-Greylist: delayed 165 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Mon, 30 Oct 2023 09:31:29 PDT Received: from p3plwbeout22-04.prod.phx3.secureserver.net (p3plsmtp22-04-2.prod.phx3.secureserver.net [68.178.252.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D74EBED for ; Mon, 30 Oct 2023 09:31:29 -0700 (PDT) Received: from mailex.mailcore.me ([94.136.40.143]) by :WBEOUT: with ESMTP id xV87q1AHYvd3NxV88qxv9l; Mon, 30 Oct 2023 09:28:44 -0700 X-CMAE-Analysis: v=2.4 cv=VI8YI/DX c=1 sm=1 tr=0 ts=653fd9bc a=EhJYbXVJKsomWlz4CTV+qA==:117 a=84ok6UeoqCVsigPHarzEiQ==:17 a=ggZhUymU-5wA:10 a=IkcTkHD0fZMA:10 a=bhdUkHdE2iEA:10 a=AUd_NHdVAAAA:8 a=FXvPX3liAAAA:8 a=RxiQ5PF5XbUlaTgh13YA:9 a=QEXdDO2ut3YA:10 a=UObqyxdv-6Yh2QiB9mM_:22 X-SECURESERVER-ACCT: phillip@squashfs.org.uk X-SID: xV87q1AHYvd3N Received: from 82-69-79-175.dsl.in-addr.zen.co.uk ([82.69.79.175] helo=[192.168.178.90]) by smtp05.mailcore.me with esmtpa (Exim 4.94.2) (envelope-from ) id 1qxV8D-0002PF-6R; Mon, 30 Oct 2023 16:28:49 +0000 Message-ID: <332ff885-f621-883a-696a-e8247fb43ecc@squashfs.org.uk> Date: Mon, 30 Oct 2023 16:28:40 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: [PATCH v2] docs: filesystems: document the squashfs specific mount options To: Ariel Miculas Cc: linux-doc@vger.kernel.org, Andrew Morton , serge@hallyn.com, Jonathan Corbet , linux-kernel@vger.kernel.org References: <20231029161924.50648-1-amiculas@cisco.com> <46d308b2-5e59-862d-b429-e6ee418bc61e@squashfs.org.uk> From: Phillip Lougher In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailcore-Auth: 439999529 X-Mailcore-Domain: 1394945 X-123-reg-Authenticated: phillip@squashfs.org.uk X-Originating-IP: 82.69.79.175 X-CMAE-Envelope: MS4xfLIBLo9MzFVKo/3fDXJ8SEJIZbHn/dw0P3cnXkWxQA/bfG6XpVa8AiM0ymCgm9s5Dz0xvNuvme3KnHbQkYS7F5hk6l1OXnRxIqr1qWCz/Kua/JFhEPzp nGoFsRAiZgJhgRw6qyObEGVqmBNo4OIyILMxF3pDFG291fhghyMxKBmg+VWKeIxr+KigMlR5YB3thMbhar53XcVsAhsOd/2rg7CZsz/CQpoPJIkeO2+TJX6t t+DLD4+ythBlN00ZqHnpsg== X-Spam-Status: No, score=-5.2 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Mon, 30 Oct 2023 09:31:44 -0700 (PDT) On 30/10/2023 16:09, Ariel Miculas wrote: > On 23/10/30 03:40PM, Phillip Lougher wrote: >> On 30/10/2023 12:57, Ariel Miculas wrote: >>> On 23/10/29 08:33PM, Phillip Lougher wrote: >>>> On 29/10/2023 16:19, Ariel Miculas wrote: >>>>> When SQUASHFS_CHOICE_DECOMP_BY_MOUNT is set, the "threads" mount option >>>>> can be used to specify the decompression mode: single-threaded, >>>>> multi-threaded, percpu or the number of threads used for decompression. >>>>> When SQUASHFS_CHOICE_DECOMP_BY_MOUNT is not set and >>>>> SQUASHFS_DECOMP_MULTI is set, the "threads" option can also be used to >>>>> specify the number of threads used for decompression. This mount option >>>>> is only mentioned in fs/squashfs/Kconfig, which makes it difficult to >>>>> find. >>>>> >>>>> Another mount option available is "errors", which can be configured to >>>>> panic the kernel when squashfs errors are encountered. >>>>> >>>>> Add both these options to the squashfs documentation, making them more >>>>> noticeable. >>>>> >>>>> Signed-off-by: Ariel Miculas >>>> >>>> Looks good to me. >>>> >>>> Reviewed-by: Phillip Lougher >>> >>> Unfortunately, it seems this is not quite correct either: >>> There is the config option SQUASHFS_MOUNT_DECOMP_THREADS: >>> ``` >>> bool "Add the mount parameter 'threads=' for squashfs" >>> depends on SQUASHFS >>> depends on SQUASHFS_DECOMP_MULTI >>> default n >>> help >>> Use threads= to set the decompression parallel mode and the number of threads. >>> If SQUASHFS_CHOICE_DECOMP_BY_MOUNT=y >>> threads= >>> else >>> threads=<2|3|...> >>> The upper limit is num_online_cpus() * 2. >>> ``` >>> that depends on SQUASHFS_DECOMP_MULTI. >>> So I think I should take my v1 patch and specify that the "threads=" >>> mount option depends on SQUASHFS_MOUNT_DECOMP_THREADS. There's no need >>> to specify SQUASHFS_DECOMP_MULTI, because SQUASHFS_MOUNT_DECOMP_THREADS >>> already depends on it. >> >> Sorry, you have to specify SQUASHFS_DECOMP_MULTI to be able to specify >> SQUASHFS_MOUNT_DECOMP_THREADS if SQUASHFS_DECOMP_BY_MOUNT is unselected. > Agree. >> >> Just try it, do make menuconfig, ensure SQUASHFS_CHOICE_DECOMP_BY_MOUNT >> is unselected, select Single threaded decompression and you won't be >> able to specify SQUASHFS_MOUNT_DECOMP_THREADS. > True. >> >> That was the point of my review. What bit don't you understand? > But SQUASHFS_DECOMP_MULTI is not enough, you need to specify > SQUASHFS_MOUNT_DECOMP_THREADS in order to use the "threads=" mount > option. > So instead of saying > ``` > If SQUASHFS_CHOICE_DECOMP_BY_MOUNT is **not** set and > SQUASHFS_DECOMP_MULTI is set: > ``` > wouldn't it be right to actually say: > ``` > If SQUASHFS_CHOICE_DECOMP_BY_MOUNT is **not** set and > SQUASHFS_MOUNT_DECOMP_THREADS is set: > ```? > > As you've mentioned, you could only set SQUASHFS_MOUNT_DECOMP_THREADS > when SQUASHFS_DECOMP_MULTI is selected. That happens in two cases: > * either SQUASHFS_CHOICE_DECOMP_BY_MOUNT is set, in which case it also > selects SQUASHFS_MOUNT_DECOMP_THREADS > * either SQUASHFS_CHOICE_DECOMP_BY_MOUNT is not set, > SQUASHFS_DECOMP_MULTI is set and SQUASHFS_MOUNT_DECOMP_THREADS is also > set > > So I wouldn't even mention SQUASHFS_DECOMP_MULTI in the documentation, > only SQUASHFS_MOUNT_DECOMP_THREADS, because the latter always depends on > the former. And the "threads=" mount option is only available when > SQUASHFS_MOUNT_DECOMP_THREADS is set (which is the configuration I've > missed in v1 and v2). > You seem determined to create an unpleasant argument here by trying to argue your first patch was correct, and I, as merely the maintainer, can't tell you to change it to how I want it. If, as you pointed out in your first patch, the purpose is to document the mount options, then the fact that threads=xxx option depends on SQUASHFS_DECOMP_MULTI being selected is important, and should be mentioned. I have accepted your V2. If you want to withdraw it now, please do so. But I will not accept further patches from you, nor respond to any more of your emails. It is never a good look to argue with the maintainer, when I am trying to help you make your patch better. You attitude means this has been a waste of my time so far. Phillip > Regards, > Ariel >> >> Phillip >> >>> What do you think? >>> >>> Regards, >>> Ariel >>> >>