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=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 9C462C33CB3 for ; Thu, 30 Jan 2020 21:11:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6CBE920708 for ; Thu, 30 Jan 2020 21:11:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="gUC0er51" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727646AbgA3VLB (ORCPT ); Thu, 30 Jan 2020 16:11:01 -0500 Received: from mail-il1-f194.google.com ([209.85.166.194]:33532 "EHLO mail-il1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbgA3VLB (ORCPT ); Thu, 30 Jan 2020 16:11:01 -0500 Received: by mail-il1-f194.google.com with SMTP id s18so4351237iln.0 for ; Thu, 30 Jan 2020 13:10:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PU5/cH0Wngrz1MgLpQX0MNgSDrR1feN6DXOeanfOIgU=; b=gUC0er5187UO/d0eIo8H6Tjx7yQ48NFKfAnXOuOddehNzaTp/7NdSTtEcR0vk6CnPx KQq74WRVprwoiDQOwaeavknl0iAx+YoJ1mcLV0k+IlX9ptMZgeKYe6N0PejT7cFrgP3I XgeaIi5meYqQB13Qy8bBQC/OTD5cR2qJOfsHaaQ/HTNNvYIwnuH4Y3p5ORPj7Yaoiqev zZeRSqysDb8V2bM3P8qOHebBNFxKOrZxTrYpF5C4al35aCS30gYSvKc2qfknefhjelYG 5yXnogmoZAzS0hn+MwWM+jpadGRI/cGgtF9p7Y0D3Y8QMjatSwvPKks6TDuDm9EjoY9z yKkg== 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=PU5/cH0Wngrz1MgLpQX0MNgSDrR1feN6DXOeanfOIgU=; b=GztRQTVdI43/UXS/O/3KcJB4VyV6bAhM7cWVStyU3VAP3ZDb97+Zqvbv8KrsH8apaC 7M1lXcnGFqSQthNogq+WQeLM6+MXiledYdC/RXHWvQhGnlOZDDX7Niv0pxlVkoTurEML 79tMY6sS76yXjInkcdLfLmmgdZZRVDu4bIfHhX2+xoaR6l3Ed+YFUnMuy+0bF5jnuIYy zvrl8JrWjvK0qWRimplqKFquoUoSL3A/UmHb8mf1ajTaBxP7Ni+Xnskl6wLh9lCrVIDI D1V3CyX3L/+WNovNkkTVkxU1IIWIVHI7W+pNRcv2OMLJjupceqffMIaVNgEvv+ZafEW5 WoFg== X-Gm-Message-State: APjAAAXj5S2W3e6QJAa41OGlX8GgXpA3DX1U8CEMApNjWigwoGi5PBET wcH+on1f5ydjNcepFhHlcQPgtKXtvdNwRQFCC3aomQ== X-Google-Smtp-Source: APXvYqzrztI9lG6S88/b67kLa+9IghKc8TeYLCFitVnLZ2reVJPOXcyj4RQJwicziNPFHZStIhjwP5IgL3SDbkxvGH0= X-Received: by 2002:a92:884e:: with SMTP id h75mr6301095ild.199.1580418658864; Thu, 30 Jan 2020 13:10:58 -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: Luigi Semenzato Date: Thu, 30 Jan 2020 13:10:47 -0800 Message-ID: Subject: Re: [PATCH 1/2] Documentation: clarify limitations of hibernation To: "Rafael J. Wysocki" Cc: Michal Hocko , Linux Memory Management List , linux-kernel , Andrew Morton , Geoff Pike Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 30, 2020 at 12:50 PM Rafael J. Wysocki wrote: > > On Mon, Jan 27, 2020 at 6:21 PM Luigi Semenzato wrote: > > > > On Mon, Jan 27, 2020 at 8:28 AM Rafael J. Wysocki wrote: > > > > > > 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. > > > > OK---I had this wrong, thanks. > > > > > > 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. > > > > Yes, that's obvious. > > > > > 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). > > > > This all makes sense, but we do this: > > > > -- add resume=/dev/sdc to the command line > > -- attach a disk (/dev/sdc) with size equal to RAM > > -- mkswap /dev/sdc > > -- swapon /dev/sdc > > -- echo disk > /sys/power/state > > > > and the last operation fails with ENOMEM. Are we doing something > > wrong? Are we hitting some other mm bug? > > I would expect this to work, so the fact that it doesn't work for you > indicates a bug somewhere or at least an assumption that doesn't hold. > > Can you please remind me what you do to trigger the unexpected behavior? Yes, I create processes that use a large amount of anon memory, more than 50% of RAM, like this: dd if=/dev/zero bs=1G count=1 | sleep infinity I think dd has a 2 GB limit, or around that number, so you'll need a few of those. Thanks!