From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E39F3C33CB7 for ; Mon, 27 Jan 2020 16:28:37 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 97227214D8 for ; Mon, 27 Jan 2020 16:28:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 97227214D8 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id DC8A16B0005; Mon, 27 Jan 2020 11:28:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id D796D6B0006; Mon, 27 Jan 2020 11:28:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C8E126B0007; Mon, 27 Jan 2020 11:28:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0047.hostedemail.com [216.40.44.47]) by kanga.kvack.org (Postfix) with ESMTP id AFD786B0005 for ; Mon, 27 Jan 2020 11:28:36 -0500 (EST) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with SMTP id 63CB42C8F for ; Mon, 27 Jan 2020 16:28:36 +0000 (UTC) X-FDA: 76423947432.22.door07_4b17c1e1b7834 X-HE-Tag: door07_4b17c1e1b7834 X-Filterd-Recvd-Size: 4624 Received: from mail-ot1-f66.google.com (mail-ot1-f66.google.com [209.85.210.66]) by imf25.hostedemail.com (Postfix) with ESMTP for ; Mon, 27 Jan 2020 16:28:35 +0000 (UTC) Received: by mail-ot1-f66.google.com with SMTP id d3so8644213otp.4 for ; Mon, 27 Jan 2020 08:28:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Jk0WC+x0mPaz/vAe6MTjly0FnoGTyiMYbm4PE77IrJc=; b=QSFyHBo7Tj7cWgNUVmwZJnsZxXNYpmGmEqPzFCNhrT0gFlh7RWisF/K6SivQ1EkhZ5 02dpeYnlC9E4eEjdZgQZNM6AUla04sA5lrsEFxV+c+L+DFYP69A4MIRvOMxz4vAxnUBo jQnfSgBMdsuFm+lUuHENvb8XagdCdMFIrKOIdG6kxsmGPtYtj3XrW0qku/9OFf/5ZgSr F5Zbw6a9u8ryARAZGP2mlFgRcZAs3Q1jAs3hRd70ItLA4go855X4Pt3szcEwAAmN4+vB c8scHn5GyO5KmSolkXkkF+IYTTvTRn2SCTHKM9r+HVUYJ62mbHVci3jzaEHSWILgijEw 9T/g== X-Gm-Message-State: APjAAAUGYCTQFlAG7Uiqb5cS8oFZ0tLMtaRugXw+RXiD4FkhcPmzTE4+ wCvrzq2d2WVEEKWBSXRuAirpJB3g/EX+viwtzkw= X-Google-Smtp-Source: APXvYqwYejxMegSnomQTuvhqcQfW89ajNLHE77TT4KoIGx8pBr8+PZXOwxMU3ebtnem4NTnutrRZ6lpHZDXnggd/0LM= X-Received: by 2002:a9d:62c7:: with SMTP id z7mr12712154otk.189.1580142515134; Mon, 27 Jan 2020 08:28:35 -0800 (PST) MIME-Version: 1.0 References: <20191226220205.128664-1-semenzato@google.com> <20191226220205.128664-2-semenzato@google.com> <20200106125352.GB9198@dhcp22.suse.cz> <20200108114952.GR32178@dhcp22.suse.cz> <20200127141637.GL1183@dhcp22.suse.cz> In-Reply-To: From: "Rafael J. Wysocki" Date: Mon, 27 Jan 2020 17:28:24 +0100 Message-ID: Subject: Re: [PATCH 1/2] Documentation: clarify limitations of hibernation To: Luigi Semenzato Cc: Michal Hocko , Linux Memory Management List , linux-kernel , "Rafael J. Wysocki" , Andrew Morton , Geoff Pike Content-Type: text/plain; charset="UTF-8" X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Jan 27, 2020 at 5:13 PM Luigi Semenzato wrote: > > On Mon, Jan 27, 2020 at 6:16 AM Michal Hocko wrote: > > > > 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. > > I am not sure what you mean by "swap" here. S2disk needs a swap > partition for storing the image, but that partition is not used for > regular swap. That's not correct. The swap partition (or file) used by s2disk needs to be made active before it can use it and the mm subsystem is also able to use it for regular swap then. > If there is no swap, but more than 50% of RAM is free > or reclaimable, s2disk works fine. If anonymous is more than 50%, > hibernation can still work, but swap needs to be set up (in addition > to the space for the hibernation image). The setup is not obvious and > I don't think that the documentation is clear on this. Well, the entire contents of RAM must be preserved, this way or another, during hibernation. That should be totally obvious to anyone using it really. Some of the RAM contents is copies of data already there in the filesystems on persistent storage and that does not need to be saved again. Everything else must be saved and s2disk (and Linux hibernation in general) uses active swap space to save these things. This implies that in order to hibernate the system, you generally need the amount of swap space equal to the size of RAM minus the size of files mapped into memory. So, to be on the safe side, the total amount of swap space to be used for hibernation needs to match the size of RAM (even though realistically it may be smaller than that in the majority of cases).