From nobody Fri Jan 2 19:06:28 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1509E95A96 for ; Mon, 9 Oct 2023 10:04:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346024AbjJIKEB (ORCPT ); Mon, 9 Oct 2023 06:04:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345822AbjJIKD6 (ORCPT ); Mon, 9 Oct 2023 06:03:58 -0400 Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7250597 for ; Mon, 9 Oct 2023 03:03:57 -0700 (PDT) Received: by mail-pl1-x633.google.com with SMTP id d9443c01a7336-1bf55a81eeaso28230175ad.0 for ; Mon, 09 Oct 2023 03:03:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopee.com; s=shopee.com; t=1696845837; x=1697450637; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=hMq2jaKv0w7qan5Rleu8o2mGnamgbpb4/RZFYckJiqE=; b=eIN6wv78V6TIKbWZslEO89bntQLmIuBcYQSWGCKiV8hx3qW1IGCESB+Oa1htaV6KpS isOAXUhyeAdED4TzYY++98CVRGuqHD4AToSEcjSRKdiJT1Vx8BwuODWuw50OFghIpAy2 cZ6kNNVgBq0tFbObLYRdD4dar+zLGyosiRu09MRlB5rTCLAbEALZZxKeCDcPXLCz10Lt 1bZXqUolgxjnIvMGDzjRNSebzBZR7z8w0bZEKlGhfNbKZ7GjtOzImAK03b+S4cO1+87L 9AdAN80jZ8+Aik7LTv5Ki7QcU3jfdon1BFoIJlXvUxJ1Ht9KBwTWP+ADnDc3a99FkEeV 7ujA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696845837; x=1697450637; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hMq2jaKv0w7qan5Rleu8o2mGnamgbpb4/RZFYckJiqE=; b=XIXhPzKzJx8huxmhmobnBmMbmpUaodZ8UUSgF32ImbiuEXYagfbqTSthdc03NRnVch 9WTFPhPE4s6nVmUomgXu5TGlC0BUn+hHCRQjC/yMnyoMMJB/aXaDXoQFCMcZ+QUcJtXm GYLelBoB7eHN/OLOioLj3KskCwZ1eAG4abS1ZlqksuAOtFP9GqFy3Snw6tbqti6+IwZc titx+cwbuHTVRvljYh/4dV+dJm78EvtJvZvcSKRdgkcRJ3NHgIxddjw/xQquZ4oGNtcI +UVAHcDFFIhvZrTQpdLT+L6QV7RzINxAQZ1KB5EVTQo8kiYb6fjISm12yWUBKBiOCNuH FtLQ== X-Gm-Message-State: AOJu0YycJ9YQu0teAj2MWy8bIKRtGeVvp5AmFVrrKp0l3dD0R/2Icm9n iMn835aMSlqocqL++JQwboRoa+FotjdH9FqWhUS12g== X-Google-Smtp-Source: AGHT+IHqyeR/SlcADUh0qh+R4VMms4WKkZS0JH3GoHyZjxjZO/4rMaaXkeB8vh9DU/H7/MsJVadC6A== X-Received: by 2002:a17:903:1245:b0:1c7:49dd:2df with SMTP id u5-20020a170903124500b001c749dd02dfmr14037224plh.32.1696845836897; Mon, 09 Oct 2023 03:03:56 -0700 (PDT) Received: from ubuntu-yizhou.default.svc.cluster.local ([101.127.248.173]) by smtp.gmail.com with ESMTPSA id d15-20020a170902cecf00b001c5eb37e92csm9119991plg.305.2023.10.09.03.03.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Oct 2023 03:03:56 -0700 (PDT) From: yizhou.tang@shopee.com To: houtao1@huawei.com, jack@suse.cz, bvanassche@acm.org, kch@nvidia.com Cc: axboe@kernel.dk, tj@kernel.org, corbet@lwn.net, linux-block@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, yingfu.zhou@shopee.com, yizhou.tang@shopee.com, chunguang.xu@shopee.com Subject: [PATCH] doc: blk-ioprio: Standardize a few names Date: Mon, 9 Oct 2023 18:03:49 +0800 Message-Id: <20231009100349.52884-1-yizhou.tang@shopee.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" From: Tang Yizhou Our system administrator have noted that the names 'rt-to-be' and 'all-to-idle' in the I/O priority policies table appeared without explanations, leading to confusion. Let's standardize these names in line with the naming in the 'attribute' section. Additionally, 1. Correct the interface name to 'io.prio.class'. 2. Add a table entry of 'promote-to-rt' for consistency. 3. Fix a typo of 'priority'. Suggested-by: Yingfu Zhou Signed-off-by: Tang Yizhou Reviewed-by: Hou Tao --- Documentation/admin-guide/cgroup-v2.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-= guide/cgroup-v2.rst index 4ef890191196..10461c73c9a3 100644 --- a/Documentation/admin-guide/cgroup-v2.rst +++ b/Documentation/admin-guide/cgroup-v2.rst @@ -2023,7 +2023,7 @@ IO Priority ~~~~~~~~~~~ =20 A single attribute controls the behavior of the I/O priority cgroup policy, -namely the blkio.prio.class attribute. The following values are accepted f= or +namely the io.prio.class attribute. The following values are accepted for that attribute: =20 no-change @@ -2052,9 +2052,11 @@ The following numerical values are associated with t= he I/O priority policies: +----------------+---+ | no-change | 0 | +----------------+---+ -| rt-to-be | 2 | +| promote-to-rt | 1 | +----------------+---+ -| all-to-idle | 3 | +| restrict-to-be | 2 | ++----------------+---+ +| idle | 3 | +----------------+---+ =20 The numerical value that corresponds to each I/O priority class is as foll= ows: @@ -2074,7 +2076,7 @@ The algorithm to set the I/O priority class for a req= uest is as follows: - If I/O priority class policy is promote-to-rt, change the request I/O priority class to IOPRIO_CLASS_RT and change the request I/O priority level to 4. -- If I/O priorityt class is not promote-to-rt, translate the I/O priority +- If I/O priority class policy is not promote-to-rt, translate the I/O pri= ority class policy into a number, then change the request I/O priority class into the maximum of the I/O priority class policy number and the numeric= al I/O priority class. --=20 2.25.1