From: Wu Fengguang <fengguang.wu@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Nigel Cunningham <nigel@tuxonice.net>,
David Rientjes <rientjes@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 6/6] PM/Hibernate: Do not try to allocate too much memory too hard
Date: Sun, 17 May 2009 20:06:13 +0800 [thread overview]
Message-ID: <20090517120613.GB3254@localhost> (raw)
In-Reply-To: <200905131042.18137.rjw@sisk.pl>
Hi Rafael,
Sorry for being late.
On Wed, May 13, 2009 at 04:42:17PM +0800, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> We want to avoid attempting to free too much memory too hard during
> hibernation, so estimate the minimum size of the image to use as the
> lower limit for preallocating memory.
>
> The approach here is based on the (experimental) observation that we
> can't free more page frames than the sum of:
>
> * global_page_state(NR_SLAB_RECLAIMABLE)
> * global_page_state(NR_ACTIVE_ANON)
> * global_page_state(NR_INACTIVE_ANON)
> * global_page_state(NR_ACTIVE_FILE)
> * global_page_state(NR_INACTIVE_FILE)
It's a very good idea to count the numbers in a reverse way.
> and even that is usually impossible to free in practice, because some
> of the pages reported as global_page_state(NR_SLAB_RECLAIMABLE) can't
> in fact be freed. It turns out, however, that if the sum of the
> above numbers is subtracted from the number of saveable pages in the
> system and the result is multiplied by 1.25, we get a suitable
> estimate of the minimum size of the image.
However, the "*1.25" looks like a hack. We should really apply more
constraints to the individual components.
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> kernel/power/snapshot.c | 56 ++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 52 insertions(+), 4 deletions(-)
>
> Index: linux-2.6/kernel/power/snapshot.c
> ===================================================================
> --- linux-2.6.orig/kernel/power/snapshot.c
> +++ linux-2.6/kernel/power/snapshot.c
> @@ -1213,6 +1213,49 @@ static void free_unnecessary_pages(void)
> }
>
> /**
> + * minimum_image_size - Estimate the minimum acceptable size of an image
> + * @saveable: The total number of saveable pages in the system.
> + *
> + * We want to avoid attempting to free too much memory too hard, so estimate the
> + * minimum acceptable size of a hibernation image to use as the lower limit for
> + * preallocating memory.
> + *
> + * The minimum size of the image is computed as
> + *
> + * ([number of saveable pages] - [number of pages we can free]) * 1.25
> + *
> + * where the second term is the sum of reclaimable slab, anonymouns pages and
> + * active/inactive file pages.
> + *
> + * NOTE: It usually turns out that we can't really free all pages reported as
> + * reclaimable slab, so the number resulting from the subtraction alone is too
> + * low. Still, it seems reasonable to assume that this number is proportional
> + * to the total number of pages that cannot be freed, which leads to the
> + * formula above. The coefficient of proportinality in this formula, 1.25, has
> + * been determined experimentally.
> + */
> +static unsigned long minimum_image_size(unsigned long saveable)
> +{
> + unsigned long size;
> +
> + /* Compute the number of saveable pages we can free. */
> + size = global_page_state(NR_SLAB_RECLAIMABLE)
> + + global_page_state(NR_ACTIVE_ANON)
> + + global_page_state(NR_INACTIVE_ANON)
> + + global_page_state(NR_ACTIVE_FILE)
> + + global_page_state(NR_INACTIVE_FILE);
For example, we could drop the 1.25 ratio and calculate the above
reclaimable size with more meaningful constraints:
/* slabs are not easy to reclaim */
size = global_page_state(NR_SLAB_RECLAIMABLE) / 2;
/* keep NR_ACTIVE_ANON */
size += global_page_state(NR_INACTIVE_ANON);
/* keep mapped files */
size += global_page_state(NR_ACTIVE_FILE);
size += global_page_state(NR_INACTIVE_FILE);
size -= global_page_state(NR_FILE_MAPPED);
That restores the hard core working set logic in the reverse way ;)
Thanks,
Fengguang
> + if (saveable <= size)
> + return saveable;
> +
> + size = saveable - size;
> + size += (size >> 2);
> +
> + return size;
> +}
> +
> +
> +/**
> * hibernate_preallocate_memory - Preallocate memory for hibernation image
> *
> * To create a hibernation image it is necessary to make a copy of every page
> @@ -1229,8 +1272,8 @@ static void free_unnecessary_pages(void)
> *
> * If image_size is set below the number following from the above formula,
> * the preallocation of memory is continued until the total number of saveable
> - * pages in the system is below the requested image size or it is impossible to
> - * allocate more memory, whichever happens first.
> + * pages in the system is below the requested image size or the minimum
> + * acceptable image size returned by minimum_image_size(), whichever is greater.
> */
> int hibernate_preallocate_memory(void)
> {
> @@ -1291,6 +1334,11 @@ int hibernate_preallocate_memory(void)
> goto out;
> }
>
> + /* Estimate the minimum size of the image. */
> + pages = minimum_image_size(saveable);
> + if (size < pages)
> + size = min_t(unsigned long, pages, max_size);
> +
> /*
> * Let the memory management subsystem know that we're going to need a
> * large number of page frames to allocate and make it free some memory.
> @@ -1303,8 +1351,8 @@ int hibernate_preallocate_memory(void)
> * The number of saveable pages in memory was too high, so apply some
> * pressure to decrease it. First, make room for the largest possible
> * image and fail if that doesn't work. Next, try to decrease the size
> - * of the image as much as indicated by image_size using allocations
> - * from highmem and non-highmem zones separately.
> + * of the image as much as indicated by 'size' using allocations from
> + * highmem and non-highmem zones separately.
> */
> pages_highmem = preallocate_image_highmem(highmem / 2);
> max_size += pages_highmem;
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-17 12:06 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905070040.08561.rjw@sisk.pl>
2009-05-07 21:48 ` [RFC][PATCH 0/5] PM/Hibernate: Rework memory shrinking (rev. 2) Rafael J. Wysocki
2009-05-07 21:50 ` [RFC][PATCH 1/5] mm: Introduce __GFP_NO_OOM_KILL Rafael J. Wysocki
2009-05-07 22:24 ` [RFC][PATCH] PM/Freezer: Disable OOM killer when tasks are frozen (was: Re: [RFC][PATCH 1/5] mm: Introduce __GFP_NO_OOM_KILL) Rafael J. Wysocki
2009-05-07 21:51 ` [RFC][PATCH 2/5] PM/Suspend: Do not shrink memory before suspend Rafael J. Wysocki
2009-05-08 8:52 ` Wu Fengguang
2009-05-07 21:51 ` [RFC][PATCH 3/5] PM/Hibernate: Move memory shrinking to snapshot.c (rev. 2) Rafael J. Wysocki
2009-05-08 8:53 ` Wu Fengguang
2009-05-07 21:53 ` [RFC][PATCH 4/5] PM/Hibernate: Rework shrinking of memory Rafael J. Wysocki
2009-05-07 21:55 ` [RFC][PATCH 5/5] PM/Hibernate: Do not release preallocated memory unnecessarily Rafael J. Wysocki
2009-05-10 13:48 ` [RFC][PATCH 0/6] PM/Hibernate: Rework memory shrinking (rev. 3) Rafael J. Wysocki
2009-05-10 13:50 ` [RFC][PATCH 1/6] mm: Introduce __GFP_NO_OOM_KILL Rafael J. Wysocki
2009-05-11 20:12 ` David Rientjes
2009-05-11 22:14 ` Rafael J. Wysocki
2009-05-11 22:33 ` Andrew Morton
2009-05-11 23:04 ` Rafael J. Wysocki
2009-05-10 13:50 ` [RFC][PATCH 2/6] PM/Suspend: Do not shrink memory before suspend Rafael J. Wysocki
2009-05-10 13:51 ` [RFC][PATCH 3/6] PM/Hibernate: Move memory shrinking to snapshot.c (rev. 2) Rafael J. Wysocki
2009-05-10 13:53 ` [RFC][PATCH 4/6] PM/Hibernate: Rework shrinking of memory Rafael J. Wysocki
2009-05-10 13:57 ` [RFC][PATCH 5/6] PM/Hibernate: Do not release preallocated memory unnecessarily Rafael J. Wysocki
2009-05-10 19:49 ` Rafael J. Wysocki
2009-05-10 14:12 ` [RFC][PATCH 6/6] PM/Hibernate: Estimate hard core working set size Rafael J. Wysocki
2009-05-10 19:53 ` Rafael J. Wysocki
2009-05-13 8:32 ` [RFC][PATCH 0/6] PM/Hibernate: Rework memory shrinking (rev. 4) Rafael J. Wysocki
2009-05-13 8:34 ` [PATCH 1/6] PM/Suspend: Do not shrink memory before suspend Rafael J. Wysocki
2009-05-13 8:35 ` [PATCH 2/6] PM/Hibernate: Move memory shrinking to snapshot.c (rev. 2) Rafael J. Wysocki
2009-05-13 8:37 ` [PATCH 3/6] mm, PM/Freezer: Disable OOM killer when tasks are frozen Rafael J. Wysocki
2009-05-13 9:19 ` Pavel Machek
2009-05-13 22:35 ` David Rientjes
2009-05-13 22:47 ` Andrew Morton
2009-05-13 23:01 ` David Rientjes
2009-05-13 8:39 ` [PATCH 4/6] PM/Hibernate: Rework shrinking of memory Rafael J. Wysocki
2009-05-13 19:34 ` Andrew Morton
2009-05-13 20:55 ` Rafael J. Wysocki
2009-05-13 21:16 ` Andrew Morton
2009-05-13 21:56 ` Rafael J. Wysocki
2009-05-14 9:40 ` Pavel Machek
2009-05-14 17:49 ` Rafael J. Wysocki
2009-05-15 13:09 ` Pavel Machek
2009-05-14 18:26 ` Rafael J. Wysocki
2009-05-13 8:40 ` [PATCH 5/6] PM/Hibernate: Do not release preallocated memory unnecessarily (rev. 2) Rafael J. Wysocki
2009-05-14 11:09 ` Pavel Machek
2009-05-14 17:52 ` Rafael J. Wysocki
2009-05-15 13:11 ` Pavel Machek
2009-05-15 14:52 ` Rafael J. Wysocki
2009-05-13 8:42 ` [RFC][PATCH 6/6] PM/Hibernate: Do not try to allocate too much memory too hard Rafael J. Wysocki
2009-05-14 11:14 ` Pavel Machek
2009-05-14 17:59 ` Rafael J. Wysocki
2009-05-15 13:14 ` Pavel Machek
2009-05-15 14:40 ` Rafael J. Wysocki
2009-05-17 12:06 ` Wu Fengguang [this message]
2009-05-17 12:55 ` Rafael J. Wysocki
2009-05-17 14:07 ` Wu Fengguang
2009-05-17 16:53 ` Rafael J. Wysocki
2009-05-18 8:32 ` Wu Fengguang
2009-05-17 21:14 ` Rafael J. Wysocki
2009-05-18 8:56 ` Wu Fengguang
2009-05-18 17:07 ` Rafael J. Wysocki
2009-05-19 0:47 ` Wu Fengguang
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=20090517120613.GB3254@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@tuxonice.net \
--cc=pavel@ucw.cz \
--cc=rientjes@google.com \
--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;
as well as URLs for NNTP newsgroup(s).