From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
linux-pm@osdl.org
Subject: Re: [RFC][PATCH 5/6] swsusp: move swap-handling functions to separate file
Date: Sun, 30 Oct 2005 14:33:25 +0100 [thread overview]
Message-ID: <20051030133325.GE657@openzaurus.ucw.cz> (raw)
In-Reply-To: <200510292241.05312.rjw@sisk.pl>
Hi!
> This patch is to show that the swap-handling part of swsusp is really independent
> and it can be moved entirely to a separate file. It introduces the file swap.c
> containing all of the swap-handling code.
>
> After the change swsusp.c contains the functions that in my opinion do not
> belong to either the snapshot-handling part or the swap-handling part
> (swsusp_suspend(), swsusp_resume() and the functions related to highmem).
Highmem handling should go to snapshot.c. Other parts do not need to know about
it.
linux-2.6.14-rc5-mm1/kernel/power/swap.c
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ linux-2.6.14-rc5-mm1/kernel/power/swap.c 2005-10-29 13:26:26.000000000 +0200
> @@ -0,0 +1,915 @@
> +/*
> + * linux/kernel/power/snapshot.c
wrong name.
> +static void dump_info(void)
> +{
> + pr_debug(" swsusp: Version: %u\n",swsusp_info.version_code);
> + pr_debug(" swsusp: Num Pages: %ld\n",swsusp_info.num_physpages);
> + pr_debug(" swsusp: UTS Sys: %s\n",swsusp_info.uts.sysname);
> + pr_debug(" swsusp: UTS Node: %s\n",swsusp_info.uts.nodename);
> + pr_debug(" swsusp: UTS Release: %s\n",swsusp_info.uts.release);
> + pr_debug(" swsusp: UTS Version: %s\n",swsusp_info.uts.version);
> + pr_debug(" swsusp: UTS Machine: %s\n",swsusp_info.uts.machine);
> + pr_debug(" swsusp: UTS Domain: %s\n",swsusp_info.uts.domainname);
> + pr_debug(" swsusp: CPUs: %d\n",swsusp_info.cpus);
> + pr_debug(" swsusp: Image: %ld Pages\n",swsusp_info.image_pages);
> + pr_debug(" swsusp: Total: %ld Pages\n", swsusp_info.pages);
> +}
I'd rather get rid of this, or at least made it *way* more terse.
Ok, that probably belongs to separate patch.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-10-30 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 19:58 [RFC][PATCH 0/6] swsusp: rework swap handling Rafael J. Wysocki
2005-10-29 20:01 ` [RFC][PATCH 1/6] swsusp: rework swsusp_suspend Rafael J. Wysocki
2005-10-29 22:25 ` Pavel Machek
2005-10-29 20:06 ` [RFC][PATCH 2/6] swsusp: move snapshot-handling functions to snapshot.c Rafael J. Wysocki
2005-10-29 22:27 ` Pavel Machek
2005-10-29 20:32 ` [RFC][PATCH 3/6] swsusp: introduce the swap map structure and interface functions Rafael J. Wysocki
2005-10-29 22:57 ` Pavel Machek
2005-10-29 23:20 ` Pavel Machek
2005-10-29 20:36 ` [RFC][PATCH 4/6] swsusp: move swap check out of swsusp_suspend Rafael J. Wysocki
2005-10-29 23:21 ` Pavel Machek
2005-10-30 12:40 ` Rafael J. Wysocki
2005-10-30 11:46 ` Pavel Machek
2005-10-29 20:41 ` [RFC][PATCH 5/6] swsusp: move swap-handling functions to separate file Rafael J. Wysocki
2005-10-30 13:33 ` Pavel Machek [this message]
2005-10-29 20:46 ` [RFC][PATCH 6/6] swsusp: improve freeing of memory Rafael J. Wysocki
2005-10-29 23:05 ` [RFC][PATCH 0/6] swsusp: rework swap handling Pavel Machek
2005-10-30 12:17 ` 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=20051030133325.GE657@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.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