From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFT][PATCH 2/3] swsusp: introduce the swap map structure
Date: Sun, 13 Nov 2005 22:16:52 +0100 [thread overview]
Message-ID: <20051113211652.GE2119@elf.ucw.cz> (raw)
In-Reply-To: <200511122122.45063.rjw@sisk.pl>
Hi!
> This patch introduces the swap map structure that can be used by swsusp for
> keeping tracks of data pages written to the swap. The structure itself is
> described in a comment within the patch.
>
> The overall idea is to reduce the amount of metadata written to the swap
> and to write and read the image pages sequentially, in a file-alike way.
> This makes the swap-handling part of swsusp fairly independent of its
> snapshot-handling part and will hopefully allow us to completely
> separate these two parts in the future.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
ACK.
> +struct swap_map_handle {
> + void *tfm; /* Needed for the encryption */
> + struct swap_map_page *cur;
> + unsigned int k;
> +};
I thought you killed encryption in 1/3?
> @@ -33,6 +33,9 @@
>
> #include "power.h"
>
> +struct pbe *pagedir_nosave = NULL;
> +unsigned int nr_copy_pages = 0;
> +
> #ifdef CONFIG_HIGHMEM
> struct highmem_page {
> char *data;
You don't need to initialize to zero/NULL.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-13 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 20:13 [RFT][PATCH 0/3] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-12 20:19 ` [RFT][PATCH 1/3] swsusp: remove encryption Rafael J. Wysocki
2005-11-12 23:42 ` Pavel Machek
2005-11-12 20:22 ` [RFT][PATCH 2/3] swsusp: introduce the swap map structure Rafael J. Wysocki
2005-11-13 21:16 ` Pavel Machek [this message]
2005-11-13 22:33 ` Rafael J. Wysocki
2005-11-12 20:24 ` [RFT][PATCH 3/3] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-13 21:14 ` Pavel Machek
2005-11-13 22:27 ` 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=20051113211652.GE2119@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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