From: Michal Hocko <mhocko@suse.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"David Rientjes" <rientjes@google.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Muchun Song" <muchun.song@linux.dev>,
"Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Usama Arif" <usama.arif@linux.dev>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Liam R . Howlett" <liam@infradead.org>,
"Yosry Ahmed" <yosry@kernel.org>,
"Rik van Riel" <riel@surriel.com>,
"Nhat Pham" <nphamcs@gmail.com>,
"Meta kernel team" <kernel-team@meta.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Robust futex causing memcg OOM storm on exit
Date: Wed, 29 Jul 2026 10:21:45 +0200 [thread overview]
Message-ID: <amm4GQP90D6Ho6Rw@tiehlicka> (raw)
In-Reply-To: <amlkSmMZTWrT4rau@linux.dev>
On Tue 28-07-26 19:25:57, Shakeel Butt wrote:
[...]
> Now I have much better results. Previous numbers were on a VM and now I have
> ran on a physical machine and the results are much better and consistent. The
> baseline consistently shows ~90 seconds exit time while (tsk_is_oom_victim +
> MMF_OOM_SKIP) consistently show ~3 seconds exit time. I will send the formal
> patch soon.
Thanks a lot for the testing Shakeel! We can always ease the check but
if the more conservative approach helps already then this would be my
preferred way.
Thanks!
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2026-07-29 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 0:19 [RFC] Robust futex causing memcg OOM storm on exit Shakeel Butt
2026-07-27 14:36 ` Michal Hocko
2026-07-27 15:38 ` Shakeel Butt
2026-07-27 20:48 ` Shakeel Butt
2026-07-28 7:27 ` Michal Hocko
2026-07-28 16:55 ` Shakeel Butt
2026-07-28 19:23 ` Michal Hocko
2026-07-28 21:57 ` Shakeel Butt
2026-07-29 2:25 ` Shakeel Butt
2026-07-29 8:21 ` Michal Hocko [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=amm4GQP90D6Ho6Rw@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=cgroups@vger.kernel.org \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=usama.arif@linux.dev \
--cc=yosry@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