From: Tejun Heo <tj@kernel.org>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Natalie Vock <natalie.vock@gmx.de>,
Maarten Lankhorst <dev@lankhorst.se>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH RESEND 1/3] docs: cgroup: Explain reclaim protection target
Date: Fri, 14 Nov 2025 11:11:26 -1000 [thread overview]
Message-ID: <aRea_mDhhsUn24K-@slm.duckdns.org> (raw)
In-Reply-To: <qhywsiwlbrpe4el3pcprtnpwdyifmfxesmsdgxuze6ho3d4wqe@mweffv3yoxlt>
On Fri, Nov 14, 2025 at 07:29:28PM +0100, Michal Koutný wrote:
> On Mon, Nov 10, 2025 at 01:00:41PM -0700, Jonathan Corbet <corbet@lwn.net> wrote:
> > > @@ -53,7 +53,8 @@ v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgrou
> > > 5-2. Memory
> > > 5-2-1. Memory Interface Files
> > > 5-2-2. Usage Guidelines
> > > - 5-2-3. Memory Ownership
> > > + 5-2-3. Reclaim Protection
> > > + 5-2-4. Memory Ownership
> >
> > I always have to ask...do we really need the manually maintained TOC
> > here?
>
> Tejun [1] (and maybe some others) like it.
I'm not married to it but I think a lot of people including me just read the
source docs without ever formatting them. It is kinda nice to have ToC for
them. Maybe section numbers are too error-prone, I don't know.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-11-14 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 19:36 [PATCH RESEND 0/3] Memory reclaim documentation fixes Michal Koutný
2025-11-10 19:36 ` [PATCH RESEND 1/3] docs: cgroup: Explain reclaim protection target Michal Koutný
2025-11-10 20:00 ` Jonathan Corbet
2025-11-14 18:29 ` Michal Koutný
2025-11-14 21:11 ` Tejun Heo [this message]
2025-11-10 19:36 ` [PATCH RESEND 2/3] docs: cgroup: Note about sibling relative reclaim protection Michal Koutný
2025-11-10 19:36 ` [PATCH RESEND 3/3] docs: cgroup: No special handling of unpopulated memcgs Michal Koutný
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=aRea_mDhhsUn24K-@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dev@lankhorst.se \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=natalie.vock@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).