From: Marc Giger <gigerstyle@gmx.ch>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Pavel Machek <pavel@ucw.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Fix SWSUSP & !SWAP
Date: Wed, 23 Apr 2003 22:36:39 +0200 [thread overview]
Message-ID: <20030423223639.7cc6a796.gigerstyle@gmx.ch> (raw)
In-Reply-To: <1051126871.1893.35.camel@laptop-linux>
Hi Nigel, Hi All
On Thu, 24 Apr 2003 07:41:11 +1200
Nigel Cunningham <ncunningham@clear.net.nz> wrote:
> Swsusp will use the portion of your swap partition that is unused when
> you start to suspend. The version currently in the 2.5 tree frees most
> of your memory before suspending, and so doesn't need that much swap at
> all. The version that I'm working on merging only frees memory if it is
> necessary to fit the image in the available swap or to have enough
> memory to be able to save the image. Thus, you need a lot more swap for
> my version. (eg. I have 640MB ram on my laptop and a ~700MB swap
> partition).
>
Ok! I see the advantages / disadvantages of each version. But what happens if the memory AND swap space are full and nothing can't be freed? When I watch the memory and swap consumption on my laptop, I think it's the most time the case...
Another question:
Is it a big problem to save the memory in a separate file on the file system, and save somewhere the pointer to it (as example in swap. Also we could set a flag in swap so that we now that the last shutdown was a hybernation). One Problem will be, that we don't know the filesystem type on resume...(We could save the module in swap...)
All that is just theoretical. It's only a idea.
Thank you for your statements.
greets
Marc
next prev parent reply other threads:[~2003-04-23 20:24 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 13:51 Pavel Machek
2003-04-23 14:32 ` Geert Uytterhoeven
2003-04-23 14:47 ` Pavel Machek
2003-04-23 15:56 ` gigerstyle
2003-04-23 19:41 ` Nigel Cunningham
2003-04-23 20:36 ` Marc Giger [this message]
2003-04-23 22:25 ` Nigel Cunningham
2003-04-23 23:28 ` Martin J. Bligh
2003-04-23 23:58 ` Pavel Machek
2003-04-23 23:55 ` Martin J. Bligh
2003-04-24 0:07 ` Andrew Morton
2003-04-24 0:17 ` CaT
2003-04-24 0:16 ` Nigel Cunningham
2003-04-24 0:26 ` Randy.Dunlap
2003-04-24 0:31 ` CaT
2003-04-24 0:38 ` Andrew Morton
2003-04-24 0:54 ` CaT
2003-04-24 1:06 ` Andrew Morton
2003-04-24 8:48 ` John Bradford
2003-04-24 0:37 ` Andrew Morton
2003-04-24 9:12 ` Pavel Machek
2003-04-24 9:25 ` Andrew Morton
2003-04-24 9:35 ` Pavel Machek
2003-04-24 9:46 ` Andrew Morton
2003-04-24 11:13 ` Nigel Cunningham
2003-04-24 11:36 ` Andrew Morton
2003-04-24 14:26 ` Pavel Machek
2003-04-24 16:37 ` Andreas Dilger
2003-04-24 20:48 ` Pavel Machek
2003-04-24 21:46 ` Andreas Dilger
2003-04-25 1:09 ` Nigel Cunningham
2003-04-25 12:59 ` Pavel Machek
2003-04-25 16:20 ` Andreas Dilger
2003-04-25 18:28 ` Nigel Cunningham
2003-04-25 19:32 ` Jamie Lokier
2003-04-25 19:58 ` Andreas Dilger
2003-04-27 18:59 ` Pavel Machek
2003-04-24 11:36 ` Geert Uytterhoeven
2003-04-25 1:22 ` H. Peter Anvin
2003-04-25 1:19 ` Nigel Cunningham
2003-04-25 1:31 ` Hua Zhong
2003-04-25 19:41 ` H. Peter Anvin
2003-04-25 4:27 ` Andreas Dilger
2003-04-25 4:33 ` H. Peter Anvin
2003-04-24 0:25 ` Pavel Machek
2003-04-24 9:01 ` Andrew Morton
2003-04-24 9:14 ` Pavel Machek
2003-04-24 9:05 ` Jamie Lokier
2003-04-24 9:34 ` Pavel Machek
2003-04-24 15:22 ` Carl-Daniel Hailfinger
2003-04-24 8:00 ` Marc Giger
2003-04-23 23:47 Grover, Andrew
2003-04-24 0:03 ` Pavel Machek
2003-04-23 23:57 ` Martin J. Bligh
2003-04-24 0:25 ` Pavel Machek
2003-04-24 0:37 ` CaT
2003-04-24 0:49 ` Martin J. Bligh
2003-04-24 9:16 ` Pavel Machek
2003-04-24 0:02 ` Nigel Cunningham
2003-04-24 0:23 ` Pavel Machek
2003-04-24 0:45 ` Martin J. Bligh
2003-04-24 3:17 ` Nigel Cunningham
2003-04-24 4:37 ` Martin J. Bligh
2003-04-24 7:49 ` Marc Giger
2003-04-24 9:27 ` Pavel Machek
2003-04-24 3:49 ` David Ford
2003-04-24 6:54 ` Jörn Engel
2003-04-24 7:01 ` Elladan
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=20030423223639.7cc6a796.gigerstyle@gmx.ch \
--to=gigerstyle@gmx.ch \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®