public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists
Date: Fri, 12 Mar 2004 11:47:55 +0000	[thread overview]
Message-ID: <20040312114755.GA17825@mail.shareable.org> (raw)
In-Reply-To: <pan.2004.03.12.11.08.02.700169@smurf.noris.de>

Matthias Urlichs wrote:
> > That effect is to cause the whole world to be swapped out when people
> > return to their machines in the morning.
> 
> The correct solution to this problem is "suspend-to-disk" --
> if the machine isn't doing anything anyway, TURN IT OFF.

How is that better for people complaining that everything needs to be
swapped in in the morning?

Suspend-to-disk will cause everything to be paged in too.  Faster I
suspect (haven't tried it; it doesn't work on my box), but still a
wait especially when you add in the BIOS boot time.

Environmentally turning an unused machine off is good.  But I don't
see how suspend-to-disk will convince people who are annoyed by
swapping in the morning.

> One slightly more practical solution from the "you-now-who gets angry
> mails" POV anyway, would be to tie the reduced-rate scanning to the load
> average -- if nothing at all happens, swap-out doesn't need to happen
> either.

If nothing at all happens, does it matter that pages are written to
swap?  They're still in RAM as well.

-- Jamie

  reply	other threads:[~2004-03-12 11:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11  0:04 [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists Nick Piggin
2004-03-11 17:25 ` Marc-Christian Petersen
2004-03-12  9:09   ` Nick Piggin
2004-03-12  9:27     ` Andrew Morton
2004-03-12  9:37       ` Nick Piggin
2004-03-12 11:08       ` Matthias Urlichs
2004-03-12 11:47         ` Jamie Lokier [this message]
2004-03-12 12:44         ` Nick Piggin
2004-03-12 14:15           ` Nick Piggin
2004-03-12 15:05             ` Nikita Danilov
2004-03-12 15:28               ` Nick Piggin
2004-03-12 16:31                 ` Nikita Danilov
2004-03-12 23:05                   ` Nick Piggin
2004-03-12 19:12             ` Andrew Morton
2004-03-12 23:23               ` Nick Piggin
2004-03-12 19:12           ` Bill Davidsen
2004-03-12 23:50             ` Nick Piggin
2004-03-12 21:46         ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-03-12 14:18 Mark_H_Johnson
2004-03-12 14:27 ` Nick Piggin
2004-03-12 19:46   ` Jamie Lokier
2004-03-12 15:00 Mark_H_Johnson
2004-03-12 15:13 ` Nick Piggin
2004-03-12 19:35   ` Jamie Lokier
2004-03-12 21:17     ` Mike Fedyk
2004-03-12 22:21       ` Jamie Lokier
2004-03-12 22:36         ` Mike Fedyk

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=20040312114755.GA17825@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smurf@smurf.noris.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