From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: Re: swsusp limits
Date: Tue, 09 Aug 2005 08:36:53 +1000 [thread overview]
Message-ID: <1123540613.7296.2.camel@localhost> (raw)
In-Reply-To: <20050808220746.GA1821@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi
On Tue, 2005-08-09 at 08:07, Pavel Machek wrote:
> > 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.
> > 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).
Regards,
Nigel
> [I'll add your questions to FAQ...]
> Pavel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-08-08 22:36 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 [this message]
2005-08-08 22:47 ` Pavel Machek
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=1123540613.7296.2.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-pm@lists.osdl.org \
--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