public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH -mm 1/2] swsusp: Free more memory
Date: Sun, 22 Apr 2007 09:31:39 +1000	[thread overview]
Message-ID: <1177198299.4036.8.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200704220005.39942.rjw@sisk.pl>


[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]

Hi.

On Sun, 2007-04-22 at 00:05 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> 
> Move the definition of PAGES_FOR_IO to kernel/power/power.h and introduce
> SPARE_PAGES representing the number of pages that should be freed by the
> swsusp's memory shrinker in addition to PAGES_FOR_IO so that device drivers can
> allocate some memory (up to 1 MB total) in their .suspend() routines without
> causing the suspend to fail.

1MB is not going to be enough for people with DRI. I have a cycle on my
machine recording 3510 extra pages (13 meg) allocated during the atomic
copy, and I know there are others with larger numbers.

Nigel

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-04-21 23:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21 22:02 [RFC][PATCH -mm 0/2] Suspend notifiers Rafael J. Wysocki
2007-04-21 22:05 ` [RFC][PATCH -mm 1/2] swsusp: Free more memory Rafael J. Wysocki
2007-04-21 23:31   ` Nigel Cunningham [this message]
2007-04-22  9:37     ` Rafael J. Wysocki
2007-04-22 22:22       ` Nigel Cunningham
2007-04-23 19:59         ` Rafael J. Wysocki
2007-04-22 12:55   ` Pavel Machek
2007-04-21 22:07 ` [RFC][PATCH -mm 2/2] PM: Introduce suspend notifiers Rafael J. Wysocki
2007-04-22 13:00   ` Pavel Machek
2007-04-22 16:14     ` 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=1177198299.4036.8.camel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --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