From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux PM <linux-pm@osdl.org>,
linux-pm@lists.osdl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Re: [RFC][PATCH -mm] swsusp: use less memory during resume
Date: Thu, 20 Apr 2006 12:05:41 +0200 [thread overview]
Message-ID: <200604201205.42421.rjw@sisk.pl> (raw)
In-Reply-To: <200604191831.45936.ncunningham@cyclades.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Hi,
On Wednesday 19 April 2006 10:31, Nigel Cunningham wrote:
> On Wednesday 19 April 2006 18:05, Rafael J. Wysocki wrote:
> > On Tuesday 18 April 2006 15:07, Nigel Cunningham wrote:
> > > On Tuesday 18 April 2006 21:19, Rafael J. Wysocki wrote:
}-- snip --{
> > > Haven't looked at the patch itself, but this sounds like a great idea. I
> > > wonder though, won't the 50% limit still apply, because you'll still have
> > > to make an atomic copy to start with (unless you figure out which pages
> > > aren't going to change and therefore don't need to be atomically copied)?
> >
> > You are right, and I'm going to figure out which pages won't change. I
> > think I have some good candidates. ;-)
>
> LRU by any chance? :)
Generally yes, but not all of them. First of all pages that are mapped by
frozen processes. Maybe some others too, but that will have to be handled
with care. ;-)
Greetings,
Rafael
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: linux-pm@lists.osdl.org, Linux PM <linux-pm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Re: [RFC][PATCH -mm] swsusp: use less memory during resume
Date: Thu, 20 Apr 2006 12:05:41 +0200 [thread overview]
Message-ID: <200604201205.42421.rjw@sisk.pl> (raw)
In-Reply-To: <200604191831.45936.ncunningham@cyclades.com>
Hi,
On Wednesday 19 April 2006 10:31, Nigel Cunningham wrote:
> On Wednesday 19 April 2006 18:05, Rafael J. Wysocki wrote:
> > On Tuesday 18 April 2006 15:07, Nigel Cunningham wrote:
> > > On Tuesday 18 April 2006 21:19, Rafael J. Wysocki wrote:
}-- snip --{
> > > Haven't looked at the patch itself, but this sounds like a great idea. I
> > > wonder though, won't the 50% limit still apply, because you'll still have
> > > to make an atomic copy to start with (unless you figure out which pages
> > > aren't going to change and therefore don't need to be atomically copied)?
> >
> > You are right, and I'm going to figure out which pages won't change. I
> > think I have some good candidates. ;-)
>
> LRU by any chance? :)
Generally yes, but not all of them. First of all pages that are mapped by
frozen processes. Maybe some others too, but that will have to be handled
with care. ;-)
Greetings,
Rafael
next prev parent reply other threads:[~2006-04-20 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 11:19 [RFC][PATCH -mm] swsusp: use less memory during resume Rafael J. Wysocki
2006-04-18 13:07 ` Nigel Cunningham
2006-04-18 13:07 ` Nigel Cunningham
2006-04-19 8:05 ` Rafael J. Wysocki
2006-04-19 8:31 ` [linux-pm] " Nigel Cunningham
2006-04-20 10:05 ` Rafael J. Wysocki [this message]
2006-04-20 10:05 ` Rafael J. Wysocki
2006-04-18 13:07 ` Pavel Machek
2006-04-18 13:07 ` 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=200604201205.42421.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-pm@osdl.org \
--cc=ncunningham@cyclades.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.