[lkml]   [2003]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Software Suspend Functionality in 2.5
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.


Suparna Bhattacharya (
Linux Technology Center
IBM Software Labs, India

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.059 / U:0.960 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site