From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stefan Seyfried <seife@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Andy Isaacson <adi@hexapodia.org>
Subject: Re: [RFC/RFT] swsusp: image size tunable (was: Re: [PATCH][mm] swsusp: limit image size)
Date: Sat, 10 Dec 2005 17:06:41 +0100 [thread overview]
Message-ID: <20051210160641.GB5047@elf.ucw.cz> (raw)
In-Reply-To: <200512101421.57918.rjw@sisk.pl>
Hi!
> > The tunable may be useful to people who'd like to achieve the
> > maximum efficiency of suspend/resume and it would be a nice
> > feature to have, I think, but let's say we'll try to implement it
> > in the future, if still needed/wanted.
>
> Actually the tunable turned out to be quite easy to implement and I think
> I'll need it for userspace swsusp (the suspend-handling userspace
> process will need to tell the kernel how much space there is for the
> image).
Looks mostly okay to me, small comments below.
> Index: linux-2.6.15-rc5-mm1/kernel/power/disk.c
> ===================================================================
> --- linux-2.6.15-rc5-mm1.orig/kernel/power/disk.c 2005-12-10 13:12:18.000000000 +0100
> +++ linux-2.6.15-rc5-mm1/kernel/power/disk.c 2005-12-10 13:20:38.000000000 +0100
> @@ -367,9 +367,34 @@
>
> power_attr(resume);
>
> +static ssize_t image_size_show(struct subsystem * subsys, char *buf)
> +{
> + return sprintf(buf, "%u\n", image_size);
> +}
> +
> +static ssize_t image_size_store(struct subsystem * subsys, const char * buf, size_t n)
> +{
> + int len;
> + char *p;
> + unsigned int size;
> +
> + p = memchr(buf, '\n', n);
> + len = p ? p - buf : n;
len and p are unused.
> + if (sscanf(buf, "%u", &size) == 1) {
> + image_size = size < MAX_IMAGE_SIZE ? size : MAX_IMAGE_SIZE;
> + return n;
Why the limit? We may want to allow very big images when someone wants
"as similar to suspended system as possible".
> Index: linux-2.6.15-rc5-mm1/kernel/power/power.h
> ===================================================================
> --- linux-2.6.15-rc5-mm1.orig/kernel/power/power.h 2005-12-10 13:12:18.000000000 +0100
> +++ linux-2.6.15-rc5-mm1/kernel/power/power.h 2005-12-10 13:20:46.000000000 +0100
> @@ -53,10 +53,12 @@
> extern struct pbe *pagedir_nosave;
>
> /*
> - * Preferred image size in MB (set it to zero to get the smallest
> + * Maximum image size in MB (set it to zero to get the smallest
> * image possible)
> */
In fact this is not maximum. If more than 500MB can't be freed, well,
it will not be freed. Very improbable, but possible.
> -#define IMAGE_SIZE 500
> +#define MAX_IMAGE_SIZE 500
> +
With runtime configuration, we should not need additional
compile-time config. OTOH /proc tunables should have descritption in
Documentation/.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-12-10 16:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:46 [PATCH][mm] swsusp: limit image size Rafael J. Wysocki
2005-12-07 21:52 ` Pavel Machek
2005-12-09 15:45 ` Stefan Seyfried
2005-12-09 15:48 ` Stefan Seyfried
2005-12-09 17:04 ` Rafael J. Wysocki
2005-12-09 18:30 ` Stefan Seyfried
2005-12-09 19:17 ` Pavel Machek
2005-12-09 22:08 ` Rafael J. Wysocki
2005-12-10 13:21 ` [RFC/RFT] swsusp: image size tunable (was: Re: [PATCH][mm] swsusp: limit image size) Rafael J. Wysocki
2005-12-10 16:06 ` Pavel Machek [this message]
2005-12-10 20:06 ` Rafael J. Wysocki
2005-12-10 22:56 ` Rafael J. Wysocki
2005-12-10 23:01 ` Pavel Machek
2005-12-16 2:09 ` Andy Isaacson
2005-12-16 10:16 ` Stefan Seyfried
2005-12-16 14:26 ` Christian Trefzer
2005-12-16 18:08 ` Rafael J. Wysocki
2005-12-16 19:29 ` Christian Trefzer
2005-12-16 21:09 ` Rafael J. Wysocki
2005-12-17 16:47 ` [RFC] swsusp: brainstorming on a freaked-out approach (was: Re: [RFC/RFT] swsusp: image size tunable) Christian Trefzer
2005-12-18 17:44 ` Pavel Machek
2005-12-18 18:24 ` [RFC] swsusp: brainstorming on a freaked-out approach Christian Trefzer
2005-12-10 22:59 ` [RFC/RFT] swsusp: image size tunable (was: Re: [PATCH][mm] swsusp: limit image size) Pavel Machek
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=20051210160641.GB5047@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=adi@hexapodia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=seife@suse.de \
/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
all inboxes | Powered by JetHome®