From: Nick Piggin <piggin@cyberone.com.au>
To: Bill Davidsen <davidsen@tmr.com>
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: Sat, 13 Mar 2004 10:50:52 +1100 [thread overview]
Message-ID: <40524CDC.8020101@cyberone.com.au> (raw)
In-Reply-To: <40520B86.50803@tmr.com>
Bill Davidsen wrote:
>
> 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 shouldn't. Perhaps something else is using memory in the background?
> 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 ;-)
>
Well it is basically just written out and reclaimed when it is needed,
it won't just be swapped out without memory pressure.
Although, there were some highmem balancing problems in 2.6 including
2.6.4 (now fixed in -bk). This causes too much pressure to be put on
ZONE_NORMAL mapped and file cache memory in favour of slab cache. This
could easily be causing the misbehaviour.
> 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.
>
There would have to be *some* memory pressure... honestly, try 2.6-bk,
or if they are production machines and you can't, then wait for 2.6.5.
next prev parent reply other threads:[~2004-03-13 0:01 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
2004-03-12 23:50 ` Nick Piggin [this message]
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=40524CDC.8020101@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=davidsen@tmr.com \
--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