All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@clear.net.nz>
To: suparna@in.ibm.com
Cc: Pavel Machek <pavel@ucw.cz>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Software Suspend Functionality in 2.5
Date: Mon, 03 Mar 2003 23:49:57 +1300	[thread overview]
Message-ID: <1046688385.1702.3.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <20030303122453.A2634@in.ibm.com>

On Mon, 2003-03-03 at 19:54, Suparna Bhattacharya wrote:
> On Mon, Mar 03, 2003 at 07:36:49PM +1300, Nigel Cunningham wrote:
> > Hi.
> > 
> > On Mon, 2003-03-03 at 17:28, Suparna Bhattacharya wrote:
> > > If you add to that the possibility of being able to save more 
> > > in less space if you have compression, would it be useful ?
> > 
> > I'm not sure that it would because we don't know how much compression
> > we're going to get ahead of time, so we don't know how many extra pages
> 
> The algorithm could be adjusted to deal with that, however ...

Ah I see. You're thinking of compressing the pages as we eat memory? I
guess I need to look at LKCD more closely. I think it can wait until we
get the basics of the expanded functionality sorted.

> 
> > we can save. The compression/decompression also takes extra time and
> > puts more drain on a potentially low battery.
> 
> .. I didn't think about the battery drain - valid point !

Of course that can be overcome too. The user simply starts swsusp
earlier or turns off compression if necessary.

Thanks for the thought provoking :>

Regards,

Nigel


  reply	other threads:[~2003-03-03 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  5:45 Software Suspend Functionality in 2.5 Nigel Cunningham
2003-02-27 12:42 ` Suparna Bhattacharya
2003-02-27 18:16   ` Nigel Cunningham
2003-02-28  6:47     ` Suparna Bhattacharya
2003-02-28 13:05       ` Pavel Machek
2003-02-28 13:39         ` Suparna Bhattacharya
2003-02-28 13:44           ` Pavel Machek
2003-02-28 15:18             ` Suparna Bhattacharya
2003-02-28 15:17               ` Pavel Machek
2003-02-28 18:59                 ` Nigel Cunningham
2003-03-03  4:28                   ` Suparna Bhattacharya
2003-03-03  6:36                     ` Nigel Cunningham
2003-03-03  6:54                       ` Suparna Bhattacharya
2003-03-03 10:49                         ` Nigel Cunningham [this message]
2003-03-03 12:25                         ` Pavel Machek
2003-03-03 13:06                           ` Suparna Bhattacharya

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=1046688385.1702.3.camel@laptop-linux.cunninghams \
    --to=ncunningham@clear.net.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=suparna@in.ibm.com \
    --cc=torvalds@transmeta.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.