Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3743301rwb; Fri, 30 Sep 2022 07:47:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4tLtN8npHwzoZGwxqT3kWmtZtXY680sTVMUsEyUXpV/IJ4Aae2yuQIfnt2SNyJpmx0/XQA X-Received: by 2002:a05:6402:185:b0:457:1489:d5fc with SMTP id r5-20020a056402018500b004571489d5fcmr7814159edv.168.1664549247435; Fri, 30 Sep 2022 07:47:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664549247; cv=none; d=google.com; s=arc-20160816; b=MMC9ogkHVS9rntveq4BQNYD8FXPWRJ5AH81+sGvUs6DlZfrA/338JbTGFNXmnrjhIp Us51zYdVb4pkNInwEyZktjpw+xm4RldnC6sRdj/1hJu5ar06HWTbfz/tETtyCyiWCcXu OdPciAJeva9ui0YZ3kQDbdpgVveRcwtwGQDuTzOhE6sSsCNhJ3tQLcpNduh1Q8MGzeVB uzAjkFJ4TnQwU+jXD0wjwwXM0BmwCsTM7fypIW5nwhFo+Dnx19NCygKtumwziIyEXk7H CnPKDyWZrbYfpC+qsHLkkPB8ybPI8jy3pdkKQ0SRgqR6ifx2ClzFyC+KQbkxot88TN+O llGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=F4PM+BzPgGypuGDwIR+Um6Xps0gQPQoLicz89LaqpZc=; b=i41aVX9XE3jJrDaOTCDLCMbJU2KlQWp2CEXvlnVtfQBGClk9/4cIB1djqE9djt2kLp n5FyMzxvwBGNPJfvZ4Z5A7RhiOxYJwYctAH5A5LZTefzN7lehjEiAeduZxT/5PMmtAlJ AcgKdutakYJRKA5wz6eGmoKKEAyJCYlwnfGzYG5Dbe4HtbUjPfeRipwumBRD3zObZniK zKUq7VoAn5MRWL+hyJUAbmgLn0wq/qsjz5Ldak9btV815Gniis+xwe9Tz+ga68vOw5ze NxmbWSf1D3d87PnYYwQjb0ZKiIXf0YczvPgXDfvXz2DgjFha5uBBKrgf4AmkkRkKw01H 81XA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s3-20020a17090699c300b007806c141214si1966416ejn.153.2022.09.30.07.47.01; Fri, 30 Sep 2022 07:47:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230079AbiI3Opv (ORCPT + 99 others); Fri, 30 Sep 2022 10:45:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53514 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230382AbiI3Opp (ORCPT ); Fri, 30 Sep 2022 10:45:45 -0400 X-Greylist: delayed 13800 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Fri, 30 Sep 2022 07:45:43 PDT Received: from 14.mo550.mail-out.ovh.net (14.mo550.mail-out.ovh.net [178.32.97.215]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0C2B7691B1 for ; Fri, 30 Sep 2022 07:45:40 -0700 (PDT) Received: from player157.ha.ovh.net (unknown [10.110.208.83]) by mo550.mail-out.ovh.net (Postfix) with ESMTP id B794620ABA for ; Fri, 30 Sep 2022 10:30:30 +0000 (UTC) Received: from sk2.org (82-65-25-201.subs.proxad.net [82.65.25.201]) (Authenticated sender: steve@sk2.org) by player157.ha.ovh.net (Postfix) with ESMTPSA id 369B12F302A5B; Fri, 30 Sep 2022 10:30:25 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-104R0059c517d12-c4be-4b6b-be74-f1dd7bd7a4d1, C05B2F2BD13FA39C9993548B485976379164E02D) smtp.auth=steve@sk2.org X-OVh-ClientIp: 82.65.25.201 From: Stephen Kitt To: Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Stephen Kitt Subject: [PATCH v2 3/5] docs: sysctl/fs: merge the aio sections Date: Fri, 30 Sep 2022 12:29:35 +0200 Message-Id: <20220930102937.135841-4-steve@sk2.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20220930102937.135841-1-steve@sk2.org> References: <20220930102937.135841-1-steve@sk2.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Ovh-Tracer-Id: 14215049276007745158 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvfedrfeehvddgvdekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvvefufffkofgjfhgggfestdekredtredttdenucfhrhhomhepufhtvghphhgvnhcumfhithhtuceoshhtvghvvgesshhkvddrohhrgheqnecuggftrfgrthhtvghrnhepgefhhfeliefghfetieffleevfefhieduheektdeghfegvdelfffgjefgtdevieegnecukfhppedtrddtrddtrddtpdekvddrieehrddvhedrvddtudenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtpdhhvghlohepphhlrgihvghrudehjedrhhgrrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpehsthgvvhgvsehskhdvrdhorhhgpdhnsggprhgtphhtthhopedupdhrtghpthhtoheplhhinhhugidqkhgvrhhnvghlsehvghgvrhdrkhgvrhhnvghlrdhorhhgpdfovfetjfhoshhtpehmohehhedt X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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 lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There are two sections documenting aio-nr and aio-max-nr, merge them. I kept the second explanation of aio-nr, which seems clearer to me, along with the effects of the values from the first section. Signed-off-by: Stephen Kitt --- Documentation/admin-guide/sysctl/fs.rst | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst index 0935acd220dc..a61c6aec5e5e 100644 --- a/Documentation/admin-guide/sysctl/fs.rst +++ b/Documentation/admin-guide/sysctl/fs.rst @@ -50,11 +50,11 @@ Currently, these files are in /proc/sys/fs: aio-nr & aio-max-nr ------------------- -aio-nr is the running total of the number of events specified on the -io_setup system call for all currently active aio contexts. If aio-nr -reaches aio-max-nr then io_setup will fail with EAGAIN. Note that -raising aio-max-nr does not result in the pre-allocation or re-sizing -of any kernel data structures. +aio-nr shows the current system-wide number of asynchronous io +requests. aio-max-nr allows you to change the maximum value +aio-nr can grow to. If aio-nr reaches aio-nr-max then io_setup will +fail with EAGAIN. Note that raising aio-max-nr does not result in the +pre-allocation or re-sizing of any kernel data structures. dentry-state @@ -287,14 +287,6 @@ mount more filesystems than the current value in super-max allows you to. -aio-nr & aio-max-nr -------------------- - -aio-nr shows the current system-wide number of asynchronous io -requests. aio-max-nr allows you to change the maximum value -aio-nr can grow to. - - mount-max --------- -- 2.31.1