public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: Re: swsusp limits
Date: Tue, 9 Aug 2005 00:47:47 +0200	[thread overview]
Message-ID: <20050808224747.GB2012@elf.ucw.cz> (raw)
In-Reply-To: <1123540613.7296.2.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

Hi!

> > > Is there an option or possibility of using a dedicated swap
> > > partition for suspend to disk?
> > > Or maybe there is no reason to think that this might help?
> > 
> > I don't see how it could help.
> 
> If it was turned on at the right time, it might not be used by other
> things that could get swapped out by high memory usage and/or the memory
> eating process.

Yes, but if it is used all the time, it will work okay, too.

> > > If my application(s) causes lots of memory & swap space
> > > to be used (over half of the total system RAM), is it correct
> > > that it is likely to be useless to try to suspend to disk
> > > while that app is running?
> > 
> > No, it should work okay, as long as you do not mlock() it. Just prepare
> > big enough swap partition.
> 
> Will he even need to worry about the size of his swap partition? I
> though swsusp discarded everything it could anyway. (Perhaps you could
> add this question to the FAQ too).

If he has *lot* of data, he needs big swap partition. Of course,
everything I _can_ discard will be discarded.

This is what I ended up:
							Pavel

diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -334,3 +334,18 @@ some kind of "really read-only!" option.
 image (and blocksize), with resume parameter pointing directly to
 suspend header.
 
+Q: Is there a maximum system RAM size that is supported by swsusp?
+
+A: It should work okay with highmem.
+
+Q: Does swsusp (to disk) use only one swap partition or can it use
+multiple swap partitions (aggregate them into one logical space)?
+
+A: Only one swap partition, sorry.
+
+Q: If my application(s) causes lots of memory & swap space to be used
+(over half of the total system RAM), is it correct that it is likely
+to be useless to try to suspend to disk while that app is running?
+
+No, it should work okay, as long as your app does not mlock() it. Just
+prepare big enough swap partition.


-- 
if you have sharp zaurus hardware you don't need... you know my address

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2005-08-08 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 20:09 swsusp limits Randy.Dunlap
2005-08-08 22:07 ` Pavel Machek
2005-08-08 22:36   ` Nigel Cunningham
2005-08-08 22:47     ` Pavel Machek [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=20050808224747.GB2012@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=ncunningham@cyclades.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