From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andy Isaacson <adi@hexapodia.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][mm][Fix] swsusp: fix counting of highmem pages
Date: Sun, 4 Dec 2005 01:10:55 +0100 [thread overview]
Message-ID: <20051204001055.GE5198@elf.ucw.cz> (raw)
In-Reply-To: <200512040102.24668.rjw@sisk.pl>
Hi!
> > Ah, okay, I see. As long as the include hack is gone, its okay with me.
>
> All right. Appended is the latest version.
Okay, seems I'll need to get latest mm version, because this changed a
lot. Sorry, that will be tommorow afternoon.
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
>
> kernel/power/snapshot.c | 25 ++++++++++++++++++-------
> kernel/power/swsusp.c | 3 ++-
> 2 files changed, 20 insertions(+), 8 deletions(-)
>
> Index: linux-2.6.15-rc3-mm1/kernel/power/snapshot.c
> ===================================================================
> --- linux-2.6.15-rc3-mm1.orig/kernel/power/snapshot.c 2005-12-03 00:14:49.000000000 +0100
> +++ linux-2.6.15-rc3-mm1/kernel/power/snapshot.c 2005-12-04 00:35:14.000000000 +0100
> @@ -37,6 +37,12 @@
> @@ -52,13 +58,12 @@
> if (!pfn_valid(pfn))
> continue;
> page = pfn_to_page(pfn);
> - if (PageReserved(page))
> - continue;
> - if (PageNosaveFree(page))
> - continue;
> - n++;
> + if (!PageNosaveFree(page) && !PageReserved(page))
> + n++;
> }
As far as I can see, this does not change anything. Can you keep it
out?
> }
> + if (n > 0)
> + n += (n * KMALLOC_SIZE + PAGE_SIZE - 1) / PAGE_SIZE + 1;
> return n;
> }
Can't you just n += n/50 here? Playing with KMALLOC_SIZE knows way too
much about memory allocation details.
> @@ -437,8 +442,14 @@
>
> static int enough_free_mem(unsigned int nr_pages)
> {
> - pr_debug("swsusp: available memory: %u pages\n", nr_free_pages());
> - return nr_free_pages() > (nr_pages + PAGES_FOR_IO +
> + struct zone *zone;
> + unsigned int n = 0;
> +
> + for_each_zone (zone)
> + if (!is_highmem(zone))
> + n += zone->free_pages;
> + pr_debug("swsusp: available memory: %u pages\n", n);
> + return n > (nr_pages + PAGES_FOR_IO +
> (nr_pages + PBES_PER_PAGE - 1) / PBES_PER_PAGE);
> }
>
Ok, so this is bugfix for different problem.
> Index: linux-2.6.15-rc3-mm1/kernel/power/swsusp.c
> ===================================================================
> --- linux-2.6.15-rc3-mm1.orig/kernel/power/swsusp.c 2005-12-03 00:14:49.000000000 +0100
> +++ linux-2.6.15-rc3-mm1/kernel/power/swsusp.c 2005-12-03 21:25:07.000000000 +0100
> @@ -635,7 +635,8 @@
> printk("Shrinking memory... ");
> do {
> #ifdef FAST_FREE
> - tmp = count_data_pages() + count_highmem_pages();
> + tmp = 2 * count_highmem_pages();
> + tmp += tmp / 50 + count_data_pages();
> tmp += (tmp + PBES_PER_PAGE - 1) / PBES_PER_PAGE +
> PAGES_FOR_IO;
> for_each_zone (zone)
And this is simple enough...
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-12-04 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 20:40 [PATCH][mm][Fix] swsusp: fix counting of highmem pages Rafael J. Wysocki
2005-12-03 21:40 ` Pavel Machek
2005-12-03 23:11 ` Rafael J. Wysocki
2005-12-03 23:50 ` Pavel Machek
2005-12-04 0:02 ` Rafael J. Wysocki
2005-12-04 0:10 ` Pavel Machek [this message]
2005-12-04 0:26 ` Rafael J. Wysocki
2005-12-04 0:35 ` Pavel Machek
2005-12-04 0:57 ` 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=20051204001055.GE5198@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=adi@hexapodia.org \
--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