archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <>
To: Evan Green <>,
	Andrew Morton <>
Cc:, Michal Hocko <>,
	Pavel Machek <>, Alex Shi <>,
	Alistair Popple <>,
	Johannes Weiner <>,
	Joonsoo Kim <>,
	"Matthew Wilcox (Oracle)" <>,
	Miaohe Lin <>,
	Minchan Kim <>,
	Suren Baghdasaryan <>,
	Vlastimil Babka <>,,
Subject: Re: [PATCH v3] mm: Enable suspend-only swap spaces
Date: Thu, 22 Jul 2021 09:12:45 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210721143946.v3.1.I09866d90c6de14f21223a03e9e6a31f8a02ecbaf@changeid>

On 21.07.21 23:40, Evan Green wrote:
> Currently it's not possible to enable hibernation without also enabling
> generic swap for a given swap area. These two use cases are not the
> same. For example there may be users who want to enable hibernation,
> but whose drives don't have the write endurance for generic swap
> activities. Swap and hibernate also have different security/integrity
> requirements, prompting folks to possibly set up something like block-level
> integrity for swap and image-level integrity for hibernate. Keeping swap
> and hibernate separate in these cases becomes not just a matter of
> preference, but correctness.
> Add a new SWAP_FLAG_NOSWAP that adds a swap region but refuses to allow
> generic swapping to it. This region can still be wired up for use in
> suspend-to-disk activities, but will never have regular pages swapped to
> it. This flag will be passed in by utilities like swapon(8), usage would
> probably look something like: swapon -o noswap /dev/sda2.

Just a minor comment, I'd call it rather SWAP_FLAG_HIBERNATE_ONLY and 
SWAP_FLAG_HIBERNATE_ONLY -- that calls the child by its name.

I think some other flags might not apply with that new flag set, right? 
For example, does SWAP_FLAG_DISCARD_ONCE or SWP_AREA_DISCARD still have 
any meaning with the new flag being set?

We should most probably disallow enabling any flag that doesn't make any 
sense in combination.

Apart from that, I'd love to see a comment in here why the workaround 
suggested by Michal isn't feasible -- essentially a summary of what we 

I had a quick glimpse and nothing jumed at me, no mm/swapfile.c expert, 
though :)


David / dhildenb

  parent reply	other threads:[~2021-07-22  7:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 21:40 Evan Green
2021-07-21 22:09 ` Andrew Morton
2021-07-22 17:16   ` Evan Green
2021-07-22  7:12 ` David Hildenbrand [this message]
2021-07-22 18:00   ` Evan Green
2021-07-23  6:58     ` David Hildenbrand
2021-07-23 17:42       ` Evan Green

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v3] mm: Enable suspend-only swap spaces' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).