From: Andrew Morton <akpm@linux-foundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Mark Brown <broonie@kernel.org>, Michal Hocko <mhocko@suse.com>,
Vlastimil Babka <vbabka@suse.cz>,
Alexey Avramov <hakavlad@inbox.lv>,
Rik van Riel <riel@surriel.com>, Mike Galbraith <efault@gmx.de>,
Darrick Wong <djwong@kernel.org>,
regressions@lists.linux.dev,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress
Date: Wed, 29 Dec 2021 15:45:53 -0800 [thread overview]
Message-ID: <20211229154553.09dd5bb657bc19d45c3de8dd@linux-foundation.org> (raw)
In-Reply-To: <caf247ab-f6fe-a3b9-c4b5-7ce17d1d5e43@leemhuis.info>
On Tue, 28 Dec 2021 11:04:18 +0100 Thorsten Leemhuis <regressions@leemhuis.info> wrote:
> Hi, this is your Linux kernel regression tracker speaking.
>
> On 02.12.21 16:06, Mel Gorman wrote:
> > Mike Galbraith, Alexey Avramov and Darrick Wong all reported similar
> > problems due to reclaim throttling for excessive lengths of time.
> > In Alexey's case, a memory hog that should go OOM quickly stalls for
> > several minutes before stalling. In Mike and Darrick's cases, a small
> > memcg environment stalled excessively even though the system had enough
> > memory overall.
>
> Just wondering: this patch afaics is now in -mm and Linux next for
> nearly two weeks. Is that intentional? I had expected it to be mainlined
> with the batch of patches Andrew mailed to Linus last week, but it
> wasn't among them.
I have it queued for 5.17-rc1.
There is still time to squeeze it into 5.16, just, with a cc:stable.
Alternatively we could merge it into 5.17-rc1 with a cc:stable, so it
will trickle back with less risk to the 5.17 release.
What do people think?
next prev parent reply other threads:[~2021-12-29 23:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:06 [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress Mel Gorman
2021-12-02 16:30 ` Shakeel Butt
2021-12-02 16:52 ` Mel Gorman
2021-12-02 17:41 ` Shakeel Butt
2021-12-03 9:01 ` Mel Gorman
2021-12-03 17:50 ` Shakeel Butt
2021-12-03 19:08 ` Mel Gorman
2021-12-06 6:06 ` Shakeel Butt
2021-12-06 11:25 ` Mel Gorman
2021-12-07 7:14 ` Shakeel Butt
2021-12-07 9:28 ` Mel Gorman
2021-12-09 6:20 ` Hugh Dickins
2021-12-09 9:53 ` Mel Gorman
2021-12-28 10:04 ` Thorsten Leemhuis
2021-12-29 23:45 ` Andrew Morton [this message]
2021-12-31 14:24 ` Thorsten Leemhuis
2021-12-31 18:33 ` Hugh Dickins
2021-12-31 19:14 ` Linus Torvalds
2021-12-31 19:21 ` Linus Torvalds
2021-12-31 19:22 ` Linus Torvalds
2022-01-01 10:52 ` Thorsten Leemhuis
2021-12-31 21:04 ` Andrew Morton
2021-12-31 21:18 ` Linus Torvalds
2022-02-14 21:10 ` Shuang Zhai
2022-02-15 14:49 ` Mel Gorman
2022-02-22 17:27 ` [PATCH v4 1/1] mm: vmscan: Reduce throttling due to a failure to make progress' Shuang Zhai
2022-02-23 12:50 ` Mel Gorman
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=20211229154553.09dd5bb657bc19d45c3de8dd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=djwong@kernel.org \
--cc=efault@gmx.de \
--cc=hakavlad@inbox.lv \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).