From: Per Olofsson <pelle@debian.org>
To: Bojan Smojver <bojan@rexursive.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10]: Hibernation: fix the number of pages used for hibernate/thaw buffering
Date: Sun, 15 Apr 2012 14:46:19 +0200 [thread overview]
Message-ID: <4F8AC31B.8010304@debian.org> (raw)
In-Reply-To: <1334266210.2573.8.camel@shrek.rexursive.com>
2012-04-12 23:30, Bojan Smojver skrev:
> I was thinking more like this:
> ----------------------
> unsigned long read_pages = 0;
>
> [...]
>
> if (low_free_pages() > snapshot_get_image_size())
> read_pages = (low_free_pages() - snapshot_get_image_size()) / 2;
> read_pages = clamp_val(read_pages, LZO_MIN_RD_PAGES, LZO_MAX_RD_PAGES);
> ----------------------
>
> Where LZO_MIN_RD_PAGES and LZO_MAX_RD_PAGES are set to 1024 and 8192,
> respectively (this was picked empirically).
>
> Because we don't really know how many highmem pages are in the image
> (this is figured out by prepare_image() function, half way through
> reading the image - so way after this calculation is done), we assume
> the worst case scenario. And that is that there are no highmem pages in
> the image.
>
> Given that we cannot use pages from highmem for buffers anyway, the
> above should be careful enough. Of course, there is still some
> possibility of running out of pages, but the kernel is usually in a
> pretty good shape memory-wise on image load, so we should be able to
> squeeze a few MBs out of it, at least.
OK, I see your point now.
Yet another reason to switch to 64-bit then I guess :-)
--
Pelle
prev parent reply other threads:[~2012-04-15 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 10:08 [PATCH v10]: Hibernation: fix the number of pages used for hibernate/thaw buffering Bojan Smojver
2012-04-12 11:31 ` Bojan Smojver
2012-04-12 16:30 ` Per Olofsson
2012-04-12 21:30 ` Bojan Smojver
2012-04-15 12:46 ` Per Olofsson [this message]
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=4F8AC31B.8010304@debian.org \
--to=pelle@debian.org \
--cc=bojan@rexursive.com \
--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