public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Oliver Neukum <oliver@neukum.org>, Pavel Machek <pavel@suse.cz>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Nigel Cunningham <ncunningham@linuxmail.org>,
	Andrew Morton <akpm@zip.com.au>,
	Stuart Young <cef-lkml@optusnet.com.au>,
	linux-kernel@vger.kernel.org, seife@suse.de
Subject: Re: swappiness=0 makes software suspend fail.
Date: Sun, 30 May 2004 22:28:07 -0500	[thread overview]
Message-ID: <200405302228.08467.rob@landley.net> (raw)
In-Reply-To: <200405310123.22136.oliver@neukum.org>

On Sunday 30 May 2004 18:23, Oliver Neukum wrote:
> Am Sonntag, 30. Mai 2004 21:47 schrieb Pavel Machek:
> > > Until something like this goes through, please don't fuglify
> > > vmscan.c any more than it is... do the saving and restoring
> > > thing that Nigel suggested please.
>
> Isn't that a race condition with setting swapiness?

During suspend?  Not really.  If it's done from the userspace script, it's 
done before the suspend is triggered, and undone after suspend comes back.  
No problem there.  If it's done in the kernel, then all the userspace 
thingies that might play with it have already been frozen, it's never touched 
from interrupt context...  What would you be locking _against_?

Swappiness isn't really twiddled from a lot of places.  Maybe your init script 
touches it.  Other than that, you have to be root, and you pretty much have 
to do it manually.  Touching this tuning knob is about as common as touching 
/proc/sys/net/ipv4/tcp_ecn or /proc/sys/kernel/panic.

The failure condition is graceful, by the way.  The suspend doesn't free 
enough memory, and thus resumes userspace immediately.  Kind of annoying if 
you've packed away your laptop to let it power down (since it can take a good 
45 seconds to do so, depending on how fragmented your swap file and memory 
and such are...)

> 	Regards
> 		Oliver

Rob

-- 
www.linucon.org: Linux Expo and Science Fiction Convention
October 8-10, 2004 in Austin Texas.  (I'm the con chair.)


  reply	other threads:[~2004-05-31  3:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28  5:00 swappiness=0 makes software suspend fail Rob Landley
2004-05-28 21:56 ` Pavel Machek
2004-05-29  7:48   ` Nigel Cunningham
2004-05-29  9:05   ` Stuart Young
2004-05-29  8:56     ` Nigel Cunningham
2004-05-29 22:23       ` Pavel Machek
2004-05-31 10:09         ` Andrew Morton
2004-05-31 10:42           ` Nick Piggin
2004-05-31 10:17         ` Andrew Morton
2004-05-31 11:38           ` Rob Landley
2004-05-31 11:52             ` Pavel Machek
2004-06-01 10:46               ` Nigel Cunningham
2004-06-03 12:08                 ` Pavel Machek
2004-05-31 22:57             ` Flavio Stanchina
2004-06-04 12:20               ` Pavel Machek
2004-05-31 11:50           ` Pavel Machek
2004-05-31 19:07             ` Stefan Seyfried
2004-05-29 22:36       ` Pavel Machek
2004-05-30  2:21         ` Nick Piggin
2004-05-30 19:47           ` Pavel Machek
2004-05-30 23:23             ` Oliver Neukum
2004-05-31  3:28               ` Rob Landley [this message]
2004-05-31  6:18             ` Stuart Young
2004-05-31  8:41               ` Pavel Machek
2004-05-29 11:35     ` 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=200405302228.08467.rob@landley.net \
    --to=rob@landley.net \
    --cc=akpm@zip.com.au \
    --cc=cef-lkml@optusnet.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=oliver@neukum.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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