From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Software Suspend Functionality in 2.5
Date: Mon, 3 Mar 2003 18:36:40 +0530 [thread overview]
Message-ID: <20030303183640.A3237@in.ibm.com> (raw)
In-Reply-To: <20030303122525.GB20929@atrey.karlin.mff.cuni.cz>; from pavel@ucw.cz on Mon, Mar 03, 2003 at 01:25:26PM +0100
On Mon, Mar 03, 2003 at 01:25:26PM +0100, Pavel Machek 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 ...
> >
> > > 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 !
>
> Actually I don't quiet think so. gzip compression is pretty cheap, and
> if it makes you suspend faster and with less disk writes...
>
> But I think it adds unneccessary complexity.
If that's the only concern left, I guess its time for us to go
back and complete what we have (we still have a few issues to
think over and concentrate on fixing), look at Nigel's patches
more closely, and then come back and discuss the algo sometime
later .. You could make up your mind about the actual complexity
then (both for suspend and resume paths).
>From what I can gather from this whole discussion, it seems
worth at least a detailed look on our part.
Thanks for the inputs and insights.
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Labs, India
prev parent reply other threads:[~2003-03-03 12:51 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
2003-03-03 12:25 ` Pavel Machek
2003-03-03 13:06 ` Suparna Bhattacharya [this message]
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=20030303183640.A3237@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox