public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org, "Yu,
	Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Andrew Morton <akpm-LJ1TwQYPT6cQrrorzV6ljw@public.gmane.org>,
	ACPI devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Linux Kernel List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [linux-pm] Re: swsusp: Not enough free pages
Date: Wed, 8 Jun 2005 17:02:52 +0200	[thread overview]
Message-ID: <200506081702.53349.rjw@sisk.pl> (raw)
In-Reply-To: <200506071239.10125.rjw-KKrjLPT3xs0@public.gmane.org>

Hi,

On Tuesday, 7 of June 2005 12:39, Rafael J. Wysocki wrote: 
> On Monday, 6 of June 2005 23:58, Pavel Machek wrote:
> > Hi!
> > 
> > > > No, I see it on i386, too. Try patch below; if it frees some after
> > > > first pass, you have that problem, too.
> > > 
> > > I've run it once and the result is this:
> > > 
> > > Freeing memory... done (75876 pages freed)
> > > Freeing memory... done (1536 pages freed)
> > > Freeing memory... done (0 pages freed)
> > > Freeing memory... done (1792 pages freed)
> > > Freeing memory... done (0 pages freed)
> > > 
> > > It does free some pages after the first pass, but this is only a small fraction
> > > of all pages freed.  I wouldn't call it a bad result ...
> > 
> > Well, it still did not free all memory it should have freed, and you
> > were lucky.
> 
> This is a reproducible behavior.  Here goes the result for another suspend:
> 
> Freeing memory... done (136611 pages freed)
> Freeing memory... done (200 pages freed)
> Freeing memory... done (128 pages freed)
> Freeing memory... done (0 pages freed)
> Freeing memory... done (2353 pages freed)
> 
> and it is always like that.  It usually frees more than 100000 pages
> in the first pass and about 5% more in the next passes together.
> 
> > Apparently for some people it does not that well (and that 
> > includes me, I see 0 in first pass quite often).
> 
> On 2.6.12-rc3+ I have never seen 0 in the first pass.  In fact, with X running
> I have never seen less than 60000. :-)
> 
> Perhaps there's a bug that does not hit x86-64 for some reason.  I'll try to
> run it on my second box later today and see what happens.

This is the worst result from the second box:

Freeing memory...  done (54641 pages freed)
Freeing memory...  done (0 pages freed)
Freeing memory...  done (5120 pages freed)
Freeing memory...  done (1952 pages freed)
Freeing memory...  done (2304 pages freed)

Still, there are 5x more pages freed in the first pass (80% of RAM was
empty anyway before suspend), and usually it is 10-20x more or so.

AFAICT, on x86-64 shrink_all_memory(10000) is good enough.

Greets,
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"


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20

  parent reply	other threads:[~2005-06-08 15:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 16:05 swsusp: Not enough free pages Yu, Luming
2005-05-24 16:55 ` Stefan Seyfried
     [not found]   ` <20050525012040.GA6145@linux.sh.intel.com>
2005-05-30  9:14     ` Yu, Luming
2005-05-30 15:01       ` Pavel Machek
     [not found]         ` <20050530150157.GC2207-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-05-30 17:01           ` James Sparenberg
2005-06-06  6:39         ` Yu, Luming
2005-06-06 10:39           ` [linux-pm] " Pavel Machek
     [not found]             ` <20050606103936.GA2520-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-06-06 17:02               ` Rafael J. Wysocki
2005-06-06 17:14                 ` Pavel Machek
2005-06-06 21:46                   ` Rafael J. Wysocki
2005-06-06 21:58                     ` Pavel Machek
     [not found]                       ` <20050606215815.GO2230-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-06-07 10:39                         ` [linux-pm] " Rafael J. Wysocki
     [not found]                           ` <200506071239.10125.rjw-KKrjLPT3xs0@public.gmane.org>
2005-06-08 15:02                             ` Rafael J. Wysocki [this message]
2005-06-08 16:27                               ` Pavel Machek
2005-06-08 21:42                                 ` [linux-pm] " Rafael J. Wysocki
2005-06-08 22:03                                   ` 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=200506081702.53349.rjw@sisk.pl \
    --to=rjw-kkrjlpt3xs0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-LJ1TwQYPT6cQrrorzV6ljw@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=pavel-AlSwsSmVLrQ@public.gmane.org \
    /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