public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>
Subject: Re: [RFC/RFT][PATCH 0/2] swsusp: improve freeing of memory
Date: Wed, 9 Nov 2005 01:32:21 +0100	[thread overview]
Message-ID: <20051109003221.GA22540@elf.ucw.cz> (raw)
In-Reply-To: <200511082355.43984.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

Hi!

> The following two patches are designed to make swsusp free only as much
> memory as needed for suspend and not as much as possible.  This speeds
> up the suspend and resume significantly and causes the system to be much
> more responsive after resume.

Yep, users will love you :-). But you need to let them know, and that
probably means cc: on linux-kernel.

If you want someone to test crypto swsusp, ask ast@domdv.de. But
removing that option is okay, too.

I still miss those "a"s in "swap".

+
+unsigned int snapshot_nr_pages(void)
+{
+       return nr_copy_pages;
+}
+
+struct pbe *snapshot_pblist(void)
+{
+       return pagedir_nosave;
+}
+
+void snapshot_pblist_set(struct pbe *pblist)
+{
+       pagedir_nosave = pblist;
+}

I really hate these. pblist_set( is the worst one. [Still improvement
from previous versions, through.] Perhaps you can just access the
variables directly?

If you really want to clean this up, swsusp_save should probably be 

int swsusp_save(struct pbe **pblist, int *nr_pages)

[that should make snapshot_nr_pages and snapshot_pblist obsolete,
right?] 

Getting rid of snapshot_pblist_set may require a bit more surgery, but
should be doable, too. swsusp_resume() should probably get struct pbe *argument...

								Pavel
-- 
Thanks, Sharp!

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



  parent reply	other threads:[~2005-11-09  0:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 22:55 [RFC/RFT][PATCH 0/2] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-08 23:06 ` [RFC/RFT][PATCH 1/2] swsusp: introduce the swap map structure Rafael J. Wysocki
2005-11-08 23:11 ` [RFC/RFT][PATCH 2/2] swsusp: improve freeing of memory Rafael J. Wysocki
2005-11-09 14:46   ` Pavel Machek
2005-11-09 22:38     ` Rafael J. Wysocki
2005-11-09 23:15       ` Pavel Machek
2005-11-10 10:12         ` Rafael J. Wysocki
2005-11-09  0:32 ` Pavel Machek [this message]
2005-11-09 22:49   ` [RFC/RFT][PATCH 0/2] " Rafael J. Wysocki
2005-11-09 23:19     ` Pavel Machek
2005-11-10 10:34       ` Rafael J. Wysocki
2005-11-10 10:48         ` Pavel Machek
2005-11-09 14:30 ` Pavel Machek
2005-11-09 21:04   ` Pavel Machek
2005-11-09 23:07     ` Rafael J. Wysocki
2005-11-09 22:55   ` Rafael J. Wysocki
2005-11-09 23:22     ` 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=20051109003221.GA22540@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@osdl.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