From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@suspend2.net>,
Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] swsusp: support creating bigger images
Date: Tue, 25 Apr 2006 12:04:09 +0200 [thread overview]
Message-ID: <20060425100408.GF4789@elf.ucw.cz> (raw)
In-Reply-To: <200604251026.53613.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi!
> > Okay, so it can be done, and patch does not look too bad. It still
> > scares me. Is 800MB image more responsive than 500MB after resume?
>
> Yes, it is, slightly, but I think 800 meg images are impractical for
> performance reasons (like IMO everything above 500 meg with the current
> hardware). However this means we can save 80% of RAM with the patch
> and that should be 400 meg instead of 250 on a 500 meg machine, or
> 200 meg instead of 125 on a 250 meg machine.
Could we get few people trying it on such small machines to see if it
is really that noticeable?
> > Is benefit worth it?
>
> Well, that depends. I think for boxes with 1 GB of RAM or more it's just
> unnecessary (as of today, but this may change if faster disks are available).
> On boxes with 512 MB of RAM or less it may change a lot as far as the
> responsiveness after resume is concerned.
>
> Anyway do you think it may go into -mm (unless Andrew shoots it down,
> that is ;-))?
I'd really like to hear that it helps someone before going to
-mm. It looks clean enough but still it is 300 lines...
Pavel
--
Thanks for all the (sleeping) penguins.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>,
Nigel Cunningham <nigel@suspend2.net>
Subject: Re: [RFC][PATCH] swsusp: support creating bigger images
Date: Tue, 25 Apr 2006 12:04:09 +0200 [thread overview]
Message-ID: <20060425100408.GF4789@elf.ucw.cz> (raw)
In-Reply-To: <200604251026.53613.rjw@sisk.pl>
Hi!
> > Okay, so it can be done, and patch does not look too bad. It still
> > scares me. Is 800MB image more responsive than 500MB after resume?
>
> Yes, it is, slightly, but I think 800 meg images are impractical for
> performance reasons (like IMO everything above 500 meg with the current
> hardware). However this means we can save 80% of RAM with the patch
> and that should be 400 meg instead of 250 on a 500 meg machine, or
> 200 meg instead of 125 on a 250 meg machine.
Could we get few people trying it on such small machines to see if it
is really that noticeable?
> > Is benefit worth it?
>
> Well, that depends. I think for boxes with 1 GB of RAM or more it's just
> unnecessary (as of today, but this may change if faster disks are available).
> On boxes with 512 MB of RAM or less it may change a lot as far as the
> responsiveness after resume is concerned.
>
> Anyway do you think it may go into -mm (unless Andrew shoots it down,
> that is ;-))?
I'd really like to hear that it helps someone before going to
-mm. It looks clean enough but still it is 300 lines...
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-04-25 10:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 21:55 [RFC][PATCH] swsusp: support creating bigger images Rafael J. Wysocki
2006-04-24 22:16 ` Pavel Machek
2006-04-25 8:26 ` Rafael J. Wysocki
2006-04-25 8:26 ` Rafael J. Wysocki
2006-04-25 10:04 ` Pavel Machek [this message]
2006-04-25 10:04 ` Pavel Machek
2006-04-25 10:31 ` Rafael J. Wysocki
2006-04-25 10:31 ` Rafael J. Wysocki
2006-04-27 15:27 ` Rafael J. Wysocki
2006-04-27 15:27 ` Rafael J. Wysocki
2006-04-27 20:55 ` Pavel Machek
2006-04-28 9:19 ` Rafael J. Wysocki
2006-04-28 9:19 ` Rafael J. Wysocki
2006-04-28 9:23 ` Pavel Machek
2006-04-28 9:23 ` Pavel Machek
2006-04-25 10:28 ` Nick Piggin
2006-04-25 15:39 ` Rafael J. Wysocki
2006-04-25 20:32 ` Pavel Machek
2006-04-25 21:12 ` Rafael J. Wysocki
2006-04-25 21:12 ` Rafael J. Wysocki
2006-04-25 21:18 ` Nigel Cunningham
2006-04-25 21:18 ` Nigel Cunningham
2006-04-25 22:21 ` Rafael J. Wysocki
2006-04-25 22:21 ` Rafael J. Wysocki
2006-04-25 22:24 ` Nigel Cunningham
2006-04-25 22:24 ` Nigel Cunningham
2006-04-25 22:38 ` Rafael J. Wysocki
2006-04-25 22:38 ` Rafael J. Wysocki
2006-04-25 22:25 ` Pavel Machek
2006-04-25 22:25 ` Pavel Machek
2006-04-25 22:30 ` Nigel Cunningham
2006-04-25 22:30 ` Nigel Cunningham
2006-04-25 22:36 ` Pavel Machek
2006-04-25 22:36 ` Pavel Machek
2006-04-25 22:43 ` Rafael J. Wysocki
2006-04-25 22:43 ` Rafael J. Wysocki
2006-04-26 0:49 ` Nigel Cunningham
2006-04-30 12:27 ` Rafael J. Wysocki
2006-04-30 12:27 ` Rafael J. Wysocki
2006-05-01 1:49 ` Nigel Cunningham
2006-05-01 1:49 ` Nigel Cunningham
2006-05-01 11:20 ` Rafael J. Wysocki
2006-05-01 22:56 ` Nigel Cunningham
2006-04-26 2:24 ` Nick Piggin
2006-04-26 2:24 ` Nick Piggin
2006-04-26 3:41 ` Nigel Cunningham
2006-04-26 16:22 ` Nick Piggin
2006-04-26 21:16 ` Rafael J. Wysocki
2006-04-26 21:16 ` Rafael J. Wysocki
2006-04-26 8:10 ` Pavel Machek
2006-04-26 8:10 ` Pavel Machek
2006-04-27 19:53 ` [RFC][PATCH] swsusp: support creating bigger images (rev. 2) Rafael J. Wysocki
2006-04-27 19:53 ` 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=20060425100408.GF4789@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=nigel@suspend2.net \
--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 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.