From: Michal Hocko <mhocko@kernel.org>
To: Luigi Semenzato <semenzato@google.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Geoff Pike <gpike@google.com>
Subject: Re: [PATCH 1/2] Documentation: clarify limitations of hibernation
Date: Mon, 27 Jan 2020 15:16:37 +0100 [thread overview]
Message-ID: <20200127141637.GL1183@dhcp22.suse.cz> (raw)
In-Reply-To: <CAA25o9Q4XP8weCNcTr1ZT9N7Y3V=B90mK8mykLOyy=-4RJ_uHQ@mail.gmail.com>
On Fri 24-01-20 08:37:12, Luigi Semenzato wrote:
[...]
> The purpose of my documentation patch was to make it clearer that
> hibernation may fail in situations in which suspend-to-RAM works; for
> instance, when there is no swap, and anonymous pages are over 50% of
> total RAM. I will send a new version of the patch which hopefully
> makes this clearer.
I was under impression that s2disk is pretty much impossible without any
swap.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-01-27 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 22:02 [PATCH 0/2] clarify limitations of hibernation Luigi Semenzato
2019-12-26 22:02 ` [PATCH 1/2] Documentation: " Luigi Semenzato
2020-01-06 12:53 ` Michal Hocko
2020-01-06 19:08 ` Luigi Semenzato
2020-01-08 11:49 ` Michal Hocko
2020-01-24 16:37 ` Luigi Semenzato
2020-01-27 14:16 ` Michal Hocko [this message]
2020-01-27 16:13 ` Luigi Semenzato
2020-01-27 16:28 ` Rafael J. Wysocki
2020-01-27 17:21 ` Luigi Semenzato
2020-01-30 20:50 ` Rafael J. Wysocki
2020-01-30 21:10 ` Luigi Semenzato
2020-01-30 21:29 ` Rafael J. Wysocki
2020-01-30 21:36 ` Luigi Semenzato
2020-01-27 16:14 ` Rafael J. Wysocki
2020-01-07 10:04 ` Rafael J. Wysocki
2019-12-26 22:02 ` [PATCH 2/2] pm: add more logging on hibernation failure Luigi Semenzato
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=20200127141637.GL1183@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gpike@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rafael@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).