public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@clear.net.nz>
To: trelane@digitasaru.net
Cc: Luke-Jr <luke7jr@yahoo.com>,
	swsusp-devel <swsusp-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Software Suspend 2.0
Date: Sat, 31 Jan 2004 20:48:29 +1300	[thread overview]
Message-ID: <1075535309.17727.79.camel@laptop-linux> (raw)
In-Reply-To: <20040131073848.GE7245@digitasaru.net>

Howdy.

On Sat, 2004-01-31 at 20:38, Joseph Pingenot wrote:
> Yay!  Yet again does annoyance reign victorious!

Well, I wouldn't really count two requests from two people as annoyance
:>

> >>   any specific way to create the swap space for saving the state to?
> >Suspend2 will use any swap space you have available. It will even
> >automatically turn on a swap partition or file for you at the start of
> >suspending, and turn it off at the end. It doesn't care about how the
> >swap space is distributed or whether it's a partition or a file or a
> >combination. Saving to local IDE and SCSI is tested, but I've had
> >limited success with SCSI due to the lack of power management on the
> >drives I was testing with (the machine resumed up to the point where it
> >wanted to use the SCSI drive again with the restored kernel, at which
> >point the driver paniced because the request numbers were out of sync).
> 
> Hmmm.  Would turning on the swap space be a better option then?  I had
>   left it off so that it wouldn't get used.

It depends how much swap gets used in your normal activity. A good rule
of thumb is to make sure you have as much swap as RAM, plus a little
more for any genuine swapping the system is doing. Then you'll be able
to save a full image without freeing up any memory... and when you do
resume, your system will be as responsive as it would be if you'd never
suspended.

> Something I was wondering about: what happens then if the swap space
>   is all filled?  I liked having a dedicated partition so that that
>   wouldn't be an issue.

If there's not swap space to store the image in, suspend tries to free
memory until there is. In the worst case, it will reach a point where it
can't free any more memory, give up and cleanly back out. (Or that's the
plan, another email I just received means I will shortly double check
this is happening correctly under 2.6).

> Hmm.  I'm hoping to take advantage of 2.6.2-rc3's ACPI updates
>   (I have some acpi wonkiness which is undoubtedly related to
>   Dell and its infamous DSDTs).  Any chance you could make that
>   your first -rc target?  :)  I'll give you a lollipop whenever
>   I see you IRL.

Haha! See what I can do.

Nigel

> Anyhow, I'm gonna hit the hay.  Thanks for the great work; you're
>   truly an asset to Kiwi-dom.  ;)

Thank you.

Nigel
-- 
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

Evolution (n): A hypothetical process whereby infinitely improbable events occur 
with alarming frequency, order arises from chaos, and no one is given credit.


  reply	other threads:[~2004-01-31  7:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30  4:24 Software Suspend 2.0 Nigel Cunningham
2004-01-30 10:04 ` Måns Rullgård
2004-01-30 10:22   ` Nigel Cunningham
2004-01-30 10:25   ` Nigel Cunningham
2004-01-31 18:09     ` Micha Feigin
2004-02-05  0:47     ` Software Suspend 2.0 [for 2.6.2 resend] Hugang
2004-01-31  6:22 ` [Swsusp-devel] Software Suspend 2.0 Luke-Jr
2004-01-31  6:37   ` Nigel Cunningham
2004-01-31  6:48     ` Joseph Pingenot
2004-01-31  6:56       ` Nigel Cunningham
2004-01-31  7:16         ` Joseph Pingenot
2004-01-31  7:28           ` Nigel Cunningham
2004-01-31  7:38             ` Joseph Pingenot
2004-01-31  7:48               ` Nigel Cunningham [this message]
2004-01-31  8:32               ` Nigel Cunningham
2004-01-31  9:03                 ` Prakash K. Cheemplavam
2004-01-31  9:08                   ` Nigel Cunningham
2004-01-31  9:19                     ` Prakash K. Cheemplavam
2004-01-31  9:51                       ` Nigel Cunningham
2004-01-31 10:43                         ` Prakash K. Cheemplavam
2004-01-31 10:48                           ` Prakash K. Cheemplavam
2004-01-31 13:25                           ` Måns Rullgård
2004-01-31 23:11                             ` Joseph Pingenot
2004-01-31 22:15                               ` Måns Rullgård
2004-02-01  0:26                               ` Micha Feigin
2004-02-01  1:48                                 ` oops with 2.6.1-rc1 and rc-3 Prakash K. Cheemplavam
2004-02-01  2:54                                   ` Micha Feigin
2004-02-01 10:36                                     ` Prakash K. Cheemplavam
2004-02-01 11:37                                       ` Prakash K. Cheemplavam
2004-01-31  9:35         ` [Swsusp-devel] Software Suspend 2.0  Éric Brunet
2004-01-31  9:38           ` Nigel Cunningham
2004-01-31  7:22     ` Luke-Jr
2004-01-31  7:31       ` Nigel Cunningham
2004-01-31  8:09         ` Luke-Jr
2004-01-31  8:11           ` Luke-Jr
2004-01-31  8:18           ` Nigel Cunningham
2004-01-31 15:23 ` Sebastian Kugler
2004-02-01  7:08 ` Hugang
2004-02-02 17:01   ` swsusp2 on ppc [Re: Software Suspend 2.0] Marco Giordani
2004-02-03  1:37     ` Hugang
2004-02-03 12:07       ` Marco Giordani

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=1075535309.17727.79.camel@laptop-linux \
    --to=ncunningham@clear.net.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke7jr@yahoo.com \
    --cc=swsusp-devel@lists.sourceforge.net \
    --cc=trelane@digitasaru.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