From: Michal Hocko <mhocko@kernel.org>
To: Luigi Semenzato <semenzato@google.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: is hibernation usable?
Date: Fri, 21 Feb 2020 09:49:10 +0100 [thread overview]
Message-ID: <20200221084910.GM20509@dhcp22.suse.cz> (raw)
In-Reply-To: <CAA25o9SCanFH3nV52BwN=7EuSUFjX=Jrd+FCiV=6ThW=beKKMw@mail.gmail.com>
On Thu 20-02-20 09:38:06, Luigi Semenzato wrote:
> I was forgetting: forcing swap by eating up memory is dangerous
> because it can lead to unexpected OOM kills
Could you be more specific what you have in mind? swapoff causing the
OOM killer?
> , but you can mitigate that
> by giving the memory-eaters a higher OOM kill score. Still, some way
> of calling try_to_free_pages() directly from user-level would be
> preferable. I wonder if such API has been discussed.
No, there is no API to trigger the global memory reclaim. You could
start the reclaim by increasing min_free_kbytes but I wouldn't really
recommend that unless you know exactly what you are doing and also I
fail to see the point. If s2disk fails due to insufficient swap space
then how can a pro-active reclaim help in the first place?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-02-21 8:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 19:50 Chris Murphy
2020-02-11 22:23 ` Luigi Semenzato
2020-02-20 2:54 ` Chris Murphy
2020-02-20 2:56 ` Chris Murphy
[not found] ` <CAA25o9T2wwqoopoNRySdZoYkD+vtqRPsB1YPnag=TkOp5D9sYA@mail.gmail.com>
2020-02-20 17:38 ` Luigi Semenzato
2020-02-21 8:49 ` Michal Hocko [this message]
2020-02-21 9:04 ` Rafael J. Wysocki
2020-02-21 9:36 ` Michal Hocko
2020-02-21 17:13 ` Luigi Semenzato
2020-02-21 9:46 ` Chris Murphy
[not found] ` <CAJCQCtScZg1CP2WTDoOy4-urPbvP_5Hw0H-AKTwHugN9YhdxLg@mail.gmail.com>
2020-02-20 19:44 ` Luigi Semenzato
2020-02-20 21:48 ` Chris Murphy
2020-02-27 6:43 ` Chris Murphy
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=20200221084910.GM20509@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=semenzato@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