mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: "Michal Koutný" <mkoutny@suse.com>, "Waiman Long" <llong@redhat.com>
Cc: Costa Shulyupin <costa.shul@redhat.com>,
	Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: Remove stale text
Date: Tue, 3 Dec 2024 13:10:59 -0500	[thread overview]
Message-ID: <6f31fcdd-82d3-4d37-a730-607ad7ada260@redhat.com> (raw)
In-Reply-To: <hjyhaosr2c5dsldlgzzsqedxzy3xd2e74ibtpxguz6ymbzqu2g@zs436iuhlnll>


On 12/3/24 12:21 PM, Michal Koutný wrote:
> On Tue, Dec 03, 2024 at 10:43:26AM GMT, Waiman Long <llong@redhat.com> wrote:
>> Thank for noticing the stale comment. There is actually no task's cpuset
>> pointer anymore.
> Yeah, that likely evolved into task_struct.cgroup css_set pointer. The
> "guidelines" for it are in sched.h/task_struct comments + comments for
> struct cgroup_subsys_state.
> Also, users may need css_get()/css_put() if they needs subsys state for
> longer. (This info isn't actually cpuset specific.)

Yes, that is likely the case though I didn't trace back the git log to 
figure out its exact evolution. Anyway, these information are optional 
as it is not cpuset specific.

Cheers,
Longman


      reply	other threads:[~2024-12-03 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  9:54 Costa Shulyupin
2024-12-03 12:31 ` Michal Koutný
2024-12-03 13:29   ` Costa Shulyupin
     [not found] ` <8a50e837-a1a0-4636-802b-4573c3779aca@redhat.com>
2024-12-03 17:21   ` Michal Koutný
2024-12-03 18:10     ` Waiman Long [this message]

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=6f31fcdd-82d3-4d37-a730-607ad7ada260@redhat.com \
    --to=llong@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=costa.shul@redhat.com \
    --cc=hannes@cmpxchg.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

all inboxes | Powered by JetHome®