cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishal Chourasia <vishalc@linux.ibm.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
	Jonathan Corbet <corbet@lwn.net>,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: cgroup: clarify controller enabling semantics
Date: Wed, 28 May 2025 23:38:00 +0530	[thread overview]
Message-ID: <aDdRAFMFY5hI2uNn@linux.ibm.com> (raw)
In-Reply-To: <bdstku24kbgj2oalpbzw62uohq7centgaz7fbeatnuymjr2qct@gp2vah7mumk3>

On Wed, May 28, 2025 at 07:05:06PM +0200, Michal Koutný wrote:
> On Wed, May 28, 2025 at 06:48:37PM +0530, Vishal Chourasia <vishalc@linux.ibm.com> wrote:
> > The part that was confused me, was the meaning behind controller being
> > available vs. enabled in a cgroup.
> > 
> > Though, the documentation does mention what it means for a controller to
> > be enabled in a cgroup later in the text. But at the point of the
> > change it is unclear.
> 
> There's a picture [1] that may be more descriptive than the docs (on
> which it is based).
Thanks for the reference. 

I didn't get the part about "io controller enabling memory controller
too". Is it referring to the fact that multiple controller can work
together in a cgroup? Because, enabling just the io controller does not
automatically enable memory controller too.

Okay, what do you suggest, should I send out V2 taking corrections from
others?

Regards,
Vishal

> 
> HTH,
> Michal
> 
> [1] https://paste.opensuse.org/pastes/987b665209bb



  reply	other threads:[~2025-05-28 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  8:53 [PATCH] Documentation: cgroup: clarify controller enabling semantics Vishal Chourasia
2025-05-27  9:58 ` Michal Koutný
2025-05-28 13:18   ` Vishal Chourasia
2025-05-28 17:05     ` Michal Koutný
2025-05-28 18:08       ` Vishal Chourasia [this message]
2025-05-28 13:31   ` Vishal Chourasia
2025-05-27 10:04 ` Bagas Sanjaya
2025-05-28 17:28   ` Vishal Chourasia
2025-05-28 15:23 ` Waiman Long
2025-05-28 15:45   ` Waiman Long
2025-05-28 17:37     ` Vishal Chourasia

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=aDdRAFMFY5hI2uNn@linux.ibm.com \
    --to=vishalc@linux.ibm.com \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --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 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).