Linux cgroups development
 help / color / mirror / Atom feed
From: Junnan Zhang <zhangjn_dev@163.com>
To: tj@kernel.org
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org,
	linux-kernel@vger.kernel.org, mkoutny@suse.com,
	ridong.chen@linux.dev, sunshx@chinatelecom.cn,
	zhangjn_dev@163.com
Subject: Re: [PATCH v3] cgroup: avoid flushing global workqueue in cgroup1_pidlist_destroy_all
Date: Thu, 10 Sep 2026 14:16:10 +0800	[thread overview]
Message-ID: <20260910061610.91209-1-zhangjn_dev@163.com> (raw)
In-Reply-To: <aqGsrY9Vj57CsVeb@slm.duckdns.org>

Hi Tejun,

Thanks for the clarification -- agreed that the 120s stall needs to
be convincingly attributed before this can count as a minimal fix.

I'll put together a reproducer that drives only cgroup churn plus
cgroup.procs readers on an otherwise idle machine, with measured
cgroup1_pidlist_destroy_all() latencies (and a lowered
hung_task_timeout_secs to catch actual splats), and report back with
the numbers. It'll take me a few days to set up.

Thanks,
Junnan


      reply	other threads:[~2026-09-10  6:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  8:40 [PATCH] cgroup: avoid flushing global workqueue in cgroup1_pidlist_destroy_all Junnan Zhang
2026-08-14  9:45 ` [PATCH v2] " Junnan Zhang
2026-08-14 10:20 ` [PATCH v3] " Junnan Zhang
2026-08-31  7:39   ` Junnan Zhang
2026-08-31  8:16   ` Michal Koutný
2026-09-01  1:53     ` Ridong Chen
2026-09-01  3:48       ` Junnan Zhang
2026-09-01  3:51       ` Junnan Zhang
     [not found]     ` <FIXME-fill-in-Michals-message-id>
2026-09-01  3:38       ` Junnan Zhang
2026-09-01  3:39       ` Junnan Zhang
2026-09-08 14:13         ` Michal Koutný
2026-09-08 16:41           ` Tejun Heo
2026-09-09  8:46             ` Junnan Zhang
2026-09-09 18:59               ` Tejun Heo
2026-09-10  6:16                 ` Junnan Zhang [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=20260910061610.91209-1-zhangjn_dev@163.com \
    --to=zhangjn_dev@163.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --cc=sunshx@chinatelecom.cn \
    --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