From: Bill Davidsen <davidsen@tmr.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Matthias Urlichs <smurf@smurf.noris.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists
Date: Fri, 12 Mar 2004 14:12:06 -0500 [thread overview]
Message-ID: <40520B86.50803@tmr.com> (raw)
In-Reply-To: <4051B0C6.2070302@cyberone.com.au>
Nick Piggin wrote:
>
>
> Matthias Urlichs wrote:
>
>> Hi, Andrew Morton 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.
>>
>>
>
> Without arguing that point, the VM also should have a solution
> to the problem where people don't turn it off.
>
>> 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.
>>
>>
>
> Well if nothing at all happens we don't swap out, but when something
> is happening, desktop users don't want any of their programs to be
> swapped out no matter how long they have been sitting idle. They don't
> want to wait 10 seconds to page something in even if it means they're
> waiting an extra 10 minutes throughout the day for their kernel greps
> and diffs to finish.
I have noticed that 2.6 seems to clear memory (any version I've run for
a while) and a lunch break results in a burst of disk activity before
the screen saver even gets in to unlock the screen. I know this box has
no cron activity during the day, so the pages were not forced out.
It's a good thing IMHO to write dirty pages to swap so the space can be
reclaimed if needed, but shouldn't the page be marked as clean and left
in memory for use without swap-in nif it's needed? I see this on backup
servers, and a machine with 3GB of free memory, no mail, no cron and no
app running isn't getting much memory pressure ;-)
I am not saying the behaviour is wrong, I just fail to see why the last
application run isn't still in memory an hour later, absent memory pressure.
--
-bill
next prev parent reply other threads:[~2004-03-12 19:07 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
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 [this message]
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=40520B86.50803@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--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