From: Tony Clarke <sam@palamon.ie>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM Related question
Date: Thu, 18 Apr 2002 16:05:14 +0100 [thread overview]
Message-ID: <3CBEE0AA.7060309@palamon.ie> (raw)
In-Reply-To: <3CBE8FBB.8080108@palamon.ie> <3CBEC025.141CAA76@aitel.hist.no>
>>I have noticed with my current kernel that after the system is idle for
>>a while, say 10 hours or
>>so, that everything seems to be swapped out to disk. So when I come in
>>the next morning
>>it starts swapping everything like crazy in from disk. Is this a known
>>characteristic of the
>>VM. I seem to remember this with all 2.4 kernels tried to date.
>>
>>Whats the point of swapping out to disk in circumstances like this?
>>
>>Currently I am using 2.4.18-rc2-ac2, with apps like mozilla, dozen
>>xterms, xemacs, staroffice etc.
>>
>
>The kernel makes no decision to swap just because you left the
>machine. But your distro probably runs "updatedb" at night.
>Updatedb reads all the directories in all your filesystems, so
>it tends to use a lot of cache. This activity pushes
>lots of other stuff into swap.
>
Yep. That makes sense. /proc/slabinfo looks like
inode_cache 60311 60312 512 8616 8616 1
dentry_cache 60301 63930 128 2131 2131 1
buffer_head 35115 40620 128 1348 1354 1
this is on a 256mb machine.
Would I be right in saying that the only way that memory gets reclaimed
, is by some process requesting memory
or by some process waking up and having a load of page faults?
Cheers,
Tony.
next prev parent reply other threads:[~2002-04-18 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 9:19 VM Related question Tony Clarke
2002-04-18 12:46 ` Helge Hafting
2002-04-18 15:05 ` Tony Clarke [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 17:35 Torrey Hoffman
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=3CBEE0AA.7060309@palamon.ie \
--to=sam@palamon.ie \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
/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