From: "Michal Koutný" <mkoutny@suse.com>
To: Tao Cui <cui.tao@linux.dev>
Cc: Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH] docs: cgroup-v2: mark memory.pressure and io.pressure as read-write
Date: Fri, 24 Jul 2026 11:42:34 +0200 [thread overview]
Message-ID: <amMzfahYd9Ua9tR1@localhost.localdomain> (raw)
In-Reply-To: <20260724020508.500893-1-cui.tao@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Fri, Jul 24, 2026 at 10:05:08AM +0800, Tao Cui <cui.tao@linux.dev> wrote:
> From: Tao Cui <cuitao@kylinos.cn>
>
> The cgroup-v2 documentation describes memory.pressure and io.pressure as
> "read-only nested-keyed file", but both files accept trigger writes
> (cgroup_memory_pressure_write / cgroup_io_pressure_write) and are therefore
> read-write. cpu.pressure and irq.pressure are already documented as
> read-write, so this also resolves an internal inconsistency.
>
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Michal Koutný <mkoutny@suse.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2026-07-24 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 2:05 [PATCH] docs: cgroup-v2: mark memory.pressure and io.pressure as read-write Tao Cui
2026-07-24 9:42 ` Michal Koutný [this message]
2026-07-26 19:47 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amMzfahYd9Ua9tR1@localhost.localdomain \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.