mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	mhocko@kernel.org, hannes@cmpxchg.org, yosryahmed@google.com,
	roman.gushchin@linux.dev, shakeel.butt@linux.dev,
	muchun.song@linux.dev, davidf@vimeo.com, handai.szj@taobao.com,
	rientjes@google.com, kamezawa.hiroyu@jp.fujitsu.com,
	RCU <rcu@vger.kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	cgroups@vger.kernel.org, chenridong@huawei.com,
	wangweiyang2@huawei.com
Subject: Re: [PATCH v3] memcg: fix soft lockup in the OOM process
Date: Mon, 13 Jan 2025 19:45:46 -0800	[thread overview]
Message-ID: <20250113194546.3de1af46fa7a668111909b63@linux-foundation.org> (raw)
In-Reply-To: <58caaa4f-cf78-4d0f-af31-8a9277b6ebf5@huaweicloud.com>

On Mon, 13 Jan 2025 14:51:55 +0800 Chen Ridong <chenridong@huaweicloud.com> wrote:

> 
> 
> On 2025/1/6 16:45, Vlastimil Babka wrote:
> > On 12/24/24 03:52, Chen Ridong wrote:
> >> From: Chen Ridong <chenridong@huawei.com>
> > 
> > +CC RCU
> > 
> >> A soft lockup issue was found in the product with about 56,000 tasks were
> >> in the OOM cgroup, it was traversing them when the soft lockup was
> >> triggered.
> >>
>
> ...
>
> >> @@ -430,10 +431,15 @@ static void dump_tasks(struct oom_control *oc)
> >>  		mem_cgroup_scan_tasks(oc->memcg, dump_task, oc);
> >>  	else {
> >>  		struct task_struct *p;
> >> +		int i = 0;
> >>  
> >>  		rcu_read_lock();
> >> -		for_each_process(p)
> >> +		for_each_process(p) {
> >> +			/* Avoid potential softlockup warning */
> >> +			if ((++i & 1023) == 0)
> >> +				touch_softlockup_watchdog();
> > 
> > This might suppress the soft lockup, but won't a rcu stall still be detected?
> 
> Yes, rcu stall was still detected.
> For global OOM, system is likely to struggle, do we have to do some
> works to suppress RCU detete?

rcu_cpu_stall_reset()?



  reply	other threads:[~2025-01-14  3:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  2:52 Chen Ridong
2024-12-24 23:06 ` David Rientjes
2025-01-03 16:18 ` Michal Koutný
2025-01-04  0:52   ` Chen Ridong
2025-01-06  8:45 ` Vlastimil Babka
2025-01-13  6:51   ` Chen Ridong
2025-01-14  3:45     ` Andrew Morton [this message]
2025-01-14  8:40       ` Michal Hocko
2025-01-14  9:20         ` Vlastimil Babka
2025-01-14  9:30           ` Michal Hocko
2025-01-14 12:19             ` Chen Ridong
2025-01-14 12:13           ` Chen Ridong
2025-01-14 18:42             ` Paul E. McKenney
2025-01-17  6:59               ` chenridong
2025-01-06  9:29 ` Michal Hocko

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=20250113194546.3de1af46fa7a668111909b63@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huawei.com \
    --cc=chenridong@huaweicloud.com \
    --cc=davidf@vimeo.com \
    --cc=handai.szj@taobao.com \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=rcu@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=vbabka@suse.cz \
    --cc=wangweiyang2@huawei.com \
    --cc=yosryahmed@google.com \
    /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®