All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haifeng Xu <haifeng.xu@shopee.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Michal Koutný" <mkoutny@suse.com>,
	lizefan.x@bytedance.com, hannes@cmpxchg.org,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: Simplify code in css_set_move_task
Date: Thu, 3 Nov 2022 22:55:19 +0800	[thread overview]
Message-ID: <830cdb70-2823-9c46-1986-2801023353d0@shopee.com> (raw)
In-Reply-To: <Y2MoBeJGU1Exg6cX@slm.duckdns.org>



On 2022/11/3 10:31, Tejun Heo wrote:
> On Thu, Nov 03, 2022 at 10:13:22AM +0800, Haifeng Xu wrote:
>> I understand your worries. Can I just check the populated state of
>> css_set in 'css_set_update_populated' and don't change the order any
>> more? I think it can also streamline 'css_set_move_task' a bit.
> 
> FWIW, I don't see much value in the proposed change. The resulting code
> isn't better in any noticeable way. Even if the change were straightforward,
> the value of the patch would seem questionable. There's no point in creating
> code churns like this. Nothing is improved in any material way while
> creating completely unnecessary risk for subtle breakages.
> 
> Thanks.
> 
Got it, thanks.

      reply	other threads:[~2022-11-03 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  7:47 [PATCH] cgroup: Simplify code in css_set_move_task haifeng.xu
2022-10-20  7:47 ` haifeng.xu
2022-10-27  8:05 ` Michal Koutný
2022-10-27  8:05   ` Michal Koutný
2022-10-28 11:29   ` Haifeng Xu
2022-10-28 11:29     ` Haifeng Xu
2022-10-31 13:11     ` Michal Koutný
2022-10-31 13:11       ` Michal Koutný
2022-11-03  2:13       ` Haifeng Xu
2022-11-03  2:13         ` Haifeng Xu
2022-11-03  2:31         ` Tejun Heo
2022-11-03  2:31           ` Tejun Heo
2022-11-03 14:55           ` Haifeng Xu [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=830cdb70-2823-9c46-1986-2801023353d0@shopee.com \
    --to=haifeng.xu@shopee.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --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 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.