public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Andy Isaacson <adi@hexapodia.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: swsusp performance problems in 2.6.15-rc3-mm1
Date: Tue, 06 Dec 2005 07:11:12 +1000	[thread overview]
Message-ID: <1133816579.3872.83.camel@localhost> (raw)
In-Reply-To: <20051205172938.GC25114@atrey.karlin.mff.cuni.cz>

Hi.

On Tue, 2005-12-06 at 03:29, Pavel Machek wrote:
> > That's not apples with apples though. If you have a hopeless battery, as
> > many do, suspend to ram is only good if you're moving from one power
> > point to another.
> 
> Yes, it is not completely fair. But as I started to use X32 with good
> battery... well I'm not really using swsusp any more.

Ah. Personally, I quite like standby mode too - no need to vga post at
all. But my lappy's battery is one of those hopeless ones, so it won't
do for long. :(

> > > * compress the image. Needs to be done in userspace, so it needs
> > > uswsusp to be merged, first. Patches for that are available. Should
> > > speed it up about twice.
> > 
> > That's not true at all. You have cryptoapi in kernel space and can
> > easily use it - it's very similar code to what you already have for
> > encryption. You won't get double the speed with with the deflate
> > compressor - more like 2 or 3MB/s :(. Suspend2 gets double the speed
> > because we use lzf, which is a logically distinction addition
> > (implemented now as another cryptoapi plugin).
> 
> Well, 3MB/sec improvement will save him  seconds on 20, or something
> like that, so I guess LZF *is* a way to go, and I'd like to keep that
> out of kernel. And I will not accept compression into mainline swsusp;
> did that experiment with encryption once already, and I did not like
> the result much.

No - I didn't mean a 3MB/s improvement. I meant that you'll get about
3MB/s throughput. It's _very_ slow. Of course having said that, I don't
recall now what machine I saw that on. It may well be my 933 Celeron
(Omnibook XE3).

> If goal is "make it work with least effort", answer is of course
> suspend2; but I need someone to help me doing it right.

How do you think suspend2 does it wrong? Is it just that you think that
everything belongs in userspace, or is there more to it?

> > > * and of course you can apply one very big patch and do all of the
> > > above :-).
> > 
> > Could you stop being nasty, please?
> 
> Sorry, I was trying to be funny.

Ok. Sorry if I over-reacted.

Regards,

Nigel


  reply	other threads:[~2005-12-05 21:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05  8:19 swsusp performance problems in 2.6.15-rc3-mm1 Andy Isaacson
2005-12-05 12:17 ` Pavel Machek
2005-12-05 13:58   ` Nigel Cunningham
2005-12-05 17:29     ` Pavel Machek
2005-12-05 21:11       ` Nigel Cunningham [this message]
2005-12-05 23:34         ` Pavel Machek
2005-12-06  1:26           ` Nigel Cunningham
2005-12-06  1:52             ` Pavel Machek
2005-12-05 22:44       ` Rafael J. Wysocki
2005-12-06  0:01         ` Pavel Machek
2005-12-05 22:28     ` Rafael J. Wysocki
2005-12-06  1:07       ` Nigel Cunningham
2005-12-06  1:37         ` Pavel Machek
2005-12-06  1:47           ` Andy Isaacson
2005-12-06  1:56             ` IDE performance on notebooks [was Re: swsusp performance problems in 2.6.15-rc3-mm1] Pavel Machek
2005-12-06  6:23               ` Andy Isaacson
2005-12-06 11:56                 ` Pavel Machek
2005-12-06  1:57             ` swsusp performance problems in 2.6.15-rc3-mm1 Nigel Cunningham
2005-12-06  3:50             ` Mark Lord
2005-12-06 15:03               ` Mark Lord
2005-12-06  2:02           ` Nigel Cunningham
2005-12-06 12:09             ` Pavel Machek
2005-12-06  1:36       ` Nigel Cunningham
2005-12-06  2:06         ` Andy Isaacson
2005-12-06  2:21           ` Nigel Cunningham
2005-12-06 14:22             ` Pavel Machek
2005-12-07 22:05               ` Nigel Cunningham
2005-12-07 22:23                 ` Pavel Machek
2005-12-06  2:21           ` Nigel Cunningham
2005-12-06 12:18           ` Pavel Machek
2005-12-06 18:15             ` Andy Isaacson
2005-12-07  1:05               ` Rafael J. Wysocki
2005-12-07  1:10                 ` Pavel Machek
2005-12-07 11:17                   ` Rafael J. Wysocki
2005-12-07 11:30                     ` Pavel Machek
2005-12-08 22:42                       ` Rafael J. Wysocki
2005-12-08 22:50                         ` Pavel Machek
2005-12-05 21:18   ` Rafael J. Wysocki
2005-12-05 23:55     ` swsusp: how much memory to free? [was Re: swsusp performance problems in 2.6.15-rc3-mm1] Pavel Machek
2005-12-07 11:53       ` Rafael J. Wysocki
2005-12-07 11:59         ` Pavel Machek
2005-12-07 12:16           ` Rafael J. Wysocki
2005-12-07 12:18             ` Pavel Machek
2005-12-05 23:05 ` swsusp performance problems in 2.6.15-rc3-mm1 Rafael J. Wysocki
2005-12-06  0:12   ` Andy Isaacson
2005-12-06  0:51     ` Pavel Machek
2005-12-10 22:21   ` Andrew Morton
2005-12-10 23:07     ` Rafael J. Wysocki
2005-12-10 23:33       ` Andrew Morton
2005-12-11 12:16         ` Rafael J. Wysocki
2005-12-11 23:28           ` Pavel Machek
2005-12-12 17:45             ` 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=1133816579.3872.83.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=adi@hexapodia.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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