linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [swsusp] Rework image freeing
Date: Thu, 22 Sep 2005 06:54:54 +0200	[thread overview]
Message-ID: <200509220654.55341.rjw@sisk.pl> (raw)
In-Reply-To: <200509220053.45358.rjw@sisk.pl>

Hi,

On Thursday, 22 of September 2005 00:53, Rafael J. Wysocki wrote:
> Hi,
> 
> On Wednesday, 21 of September 2005 22:51, Pavel Machek wrote:
> > Do not store pagedirs in swap twice. This needed rewrite of image
> > freeing, but it enabled me nice cleanups in the end.
> > 
> > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > 
> > ---
> > commit 67434821951d6f10d55e29465a24e7f5015038f1
> > tree ee0f4a209e8b680ffdfa6e7837a3a248b524f421
> > parent 7bdc8fc378f053bd4eb4210beb1d494485318512
> > author <pavel@amd.(none)> Tue, 20 Sep 2005 15:34:55 +0200
> > committer <pavel@amd.(none)> Tue, 20 Sep 2005 15:34:55 +0200
> > 
> >  kernel/power/swsusp.c |  103 ++++++++++++++++++++++---------------------------
> >  1 files changed, 46 insertions(+), 57 deletions(-)
> > 
> > diff --git a/kernel/power/swsusp.c b/kernel/power/swsusp.c
> > --- a/kernel/power/swsusp.c
> > +++ b/kernel/power/swsusp.c
> > @@ -729,16 +729,6 @@ static void copy_data_pages(void)
> >  	BUG_ON(pbe);
> >  }
> >  
> > -
> > -/**
> > - *	calc_nr - Determine the number of pages needed for a pbe list.
> > - */
> > -
> > -static int calc_nr(int nr_copy)
> > -{
> > -	return nr_copy + (nr_copy+PBES_PER_PAGE-2)/(PBES_PER_PAGE-1);
> > -}
> 
> I can't see why you are going to drop this function.  Isn't it necessary any more?

OK, swsusp fails anyway when it cannot allocate a page, so in fact it is not.
However, the information printed in swsusp_alloc():

>  /**
>   *	enough_free_mem - Make sure we enough free memory to snapshot.
> @@ -914,19 +895,23 @@ static int enough_swap(void)
>  
>  static int swsusp_alloc(void)
>  {
> -	int error;
> +	struct pbe *p;
>  
>  	pagedir_nosave = NULL;
> -	nr_copy_pages = calc_nr(nr_copy_pages);
>  
>  	pr_debug("suspend: (pages needed: %d + %d free: %d)\n",
>  		 nr_copy_pages, PAGES_FOR_IO, nr_free_pages());

now seems to be inaccurate, because we likely need more pages than
 nr_copy_pages + PAGES_FOR_IO.

Greetings,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-09-22  4:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 20:51 [swsusp] Rework image freeing Pavel Machek
2005-09-21 20:58 ` Andrew Morton
2005-09-21 21:19   ` Pavel Machek
2005-09-21 21:31     ` Andrew Morton
2005-09-21 21:11 ` Dave Hansen
2005-09-21 21:18 ` Dave Hansen
2005-09-21 21:23   ` Pavel Machek
2005-09-21 22:53 ` Rafael J. Wysocki
2005-09-22  4:54   ` Rafael J. Wysocki [this message]
2005-09-22  9:46   ` Pavel Machek
2005-09-23 20:52     ` Rafael J. Wysocki
2005-09-23 21:19       ` 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=200509220654.55341.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).