From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp with highmem, testing wanted
Date: Fri, 26 Mar 2004 00:54:40 +0100 [thread overview]
Message-ID: <20040325235440.GL2179@elf.ucw.cz> (raw)
In-Reply-To: <1080254675.7097.16.camel@calvin.wpcb.org.au>
Hi!
> On Fri, 2004-03-26 at 10:59, Pavel Machek wrote:
> > > I also think we free too much memory btw (and spend too much time
> > > trying to free memory). Have you looked at some of Nigel stuffs in
> > > swsusp2 ? There may be good ideas to borrow...
> >
> > Yes, swsusp2 is faster. It is also 10x more code. We could probably
> > stop freeing as soon as half of memory is free; OTOH if memory is
> > disk cache, it might be faster to drop it than write to swap, then
> > read back [swsusp2 shows its not usually the case, through].
>
> 10x more code is true, but we also need to ask, how much of that is more
> functionality? How much is debugging code (that can be removed)? How
> much is comments?
Do you think you could strip down features + debugging etc so that
swsusp2 is only, say, 3x bigger than swsusp1? It would certainly make
merging easier.
> 10x implies there's needless bloat and that the two are otherwise
> equivalent. That's simply not true.
If I implied that I should appologize. (Sorry.) swsusp2 *has* more
features, many of them make it faster.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-25 23:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 23:57 swsusp with highmem, testing wanted Pavel Machek
2004-03-25 3:28 ` Benjamin Herrenschmidt
[not found] ` <20040325120250.GC300@elf.ucw.cz>
2004-03-25 22:41 ` Benjamin Herrenschmidt
2004-03-25 22:59 ` Pavel Machek
2004-03-25 22:44 ` Nigel Cunningham
2004-03-25 23:54 ` Pavel Machek [this message]
2004-03-25 23:06 ` Nigel Cunningham
2004-03-26 0:22 ` Benjamin Herrenschmidt
2004-03-25 3:48 ` Jeff Chua
[not found] ` <20040325073244.GE3377@suse.de>
[not found] ` <20040325115129.GB300@elf.ucw.cz>
[not found] ` <20040325121418.GK3377@suse.de>
2004-03-25 15:01 ` Pavel Machek
2004-03-25 15:27 ` Jens Axboe
2004-03-25 22:22 ` Pavel Machek
2004-03-26 14:09 ` Jens Axboe
2004-03-26 14:34 ` Pavel Machek
[not found] ` <20040325100339.GN791@holomorphy.com>
2004-03-25 21:59 ` Pavel Machek
2004-03-26 12:03 ` William Lee Irwin III
2004-03-26 12:08 ` Pavel Machek
2004-03-26 12:36 ` William Lee Irwin III
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=20040325235440.GL2179@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
/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