From: Alexey Avramov <hakavlad@inbox.lv>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mhocko@suse.com, vbabka@suse.cz, neilb@suse.de,
akpm@linux-foundation.org, corbet@lwn.net, riel@surriel.com,
hannes@cmpxchg.org, david@fromorbit.com, willy@infradead.org,
hdanton@sina.com, penguin-kernel@i-love.sakura.ne.jp,
oleksandr@natalenko.name, kernel@xanmod.org,
michael@michaellarabel.com, aros@gmx.com, hakavlad@gmail.com
Subject: Re: mm: 5.16 regression: reclaim_throttle leads to stall in near-OOM conditions
Date: Wed, 24 Nov 2021 19:54:49 +0900 [thread overview]
Message-ID: <20211124195449.33f31e7f@mail.inbox.lv> (raw)
In-Reply-To: <20211124103550.GE3366@techsingularity.net>
> it does eventually get killed OOM
However, a full minute freeze can be a great evil in many situations -
during such a freeze, the system is completely unresponsive.
So my next question is: How reasonable is the value MAX_RECLAIM_RETRIES?
Is it also get "out of thin air"?
And would it make sense to have buttons to adjust the timeouts?
next prev parent reply other threads:[~2021-11-24 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 16:19 mm: 5.16 regression: reclaim_throttle leads to stall in near-OOM conditions Alexey Avramov
2021-11-24 7:40 ` Thorsten Leemhuis
2021-11-24 10:35 ` Mel Gorman
2021-11-24 10:54 ` Alexey Avramov [this message]
2021-11-24 11:50 ` Mel Gorman
2021-11-24 12:03 ` Alexey Avramov
2021-11-24 12:44 ` Alexey Avramov
2021-11-24 14:33 ` Mel Gorman
2021-11-26 16:06 ` Alexey Avramov
2021-11-26 16:24 ` Mel Gorman
2021-12-20 8:50 ` Sultan Alsawaf
2021-11-27 19:37 ` Alexey Avramov
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=20211124195449.33f31e7f@mail.inbox.lv \
--to=hakavlad@inbox.lv \
--cc=akpm@linux-foundation.org \
--cc=aros@gmx.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=hakavlad@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=kernel@xanmod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=michael@michaellarabel.com \
--cc=neilb@suse.de \
--cc=oleksandr@natalenko.name \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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