From: Chris Down <chris@chrisdown.name>
To: Luigi Semenzato <semenzato@google.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 1/2] Documentation: clarify limitations of hibernation
Date: Sat, 28 Dec 2019 00:23:09 +0000 [thread overview]
Message-ID: <20191228002309.GA544630@chrisdown.name> (raw)
In-Reply-To: <20191227213439.139123-2-semenzato@google.com>
Luigi Semenzato writes:
>+One possible workaround (besides terminating enough processes) is to force
>+excess anonymous pages out to swap before hibernating. This can be achieved
>+with memcgroups, by lowering memory usage limits with ``echo <new limit> >
s/memcgroups/memory cgroups/
I also wouldn't say "excess", it implies that the cold(er) pages are
unnecessary, which may not be true.
>+/dev/cgroup/memory/<group>/memory.mem.usage_in_bytes``. However, the latter
>+operation is not guaranteed to succeed.
This is cgroup v1, which is frozen and in the process of being deprecated. We
should at least mention memory.high or similar.
Also, /dev/cgroup? /sys/fs/cgroup has been more or less standardised for quite
a while now...
(I also wonder whether the need for this in general is something the user
shouldn't have to care about and we should improve management of in-kernel, but
I know very little about hibernation so I'll leave that alone.)
next prev parent reply other threads:[~2019-12-28 0:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 21:34 [PATCH 0/2] clarify limitations of hibernation Luigi Semenzato
2019-12-27 21:34 ` [PATCH 1/2] Documentation: " Luigi Semenzato
2019-12-28 0:23 ` Chris Down [this message]
2019-12-28 0:25 ` Chris Down
2020-01-02 19:29 ` Luigi Semenzato
2019-12-27 21:34 ` [PATCH 2/2] pm: add more logging on hibernation failure Luigi Semenzato
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20191228002309.GA544630@chrisdown.name \
--to=chris@chrisdown.name \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.