From: Mike Fedyk <mfedyk@matchmail.com>
To: David Chow <davidchow@rcn.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dirty Page cache in 2.4
Date: Mon, 5 Nov 2001 19:04:17 -0800 [thread overview]
Message-ID: <20011105190417.A665@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3BE7513D.40403@rcn.com.hk>
In-Reply-To: <3BE7513D.40403@rcn.com.hk>
On Tue, Nov 06, 2001 at 10:55:57AM +0800, David Chow wrote:
> Dear all,
>
> I've heard the memory management in 2.4 swap out dirty pages. Is it true
> that dirty pages refer to the dirty pages of page cache and they may
> also be swapped out? Thanks.
>
No, very untrue.
To be more specific, there are dirty filesystem cache pages, and dirty
application pages. Dirty filesystem pages will be written to the FS, while
dirty application pages will be swapped out.
If an application page is chosen for swap out and it is not dirty, the VM
will just discard that page completely because it can beloaded from the app
or library on disk when needed again...
BTW, both VMs would do this. This behavior is very fundamental to VM design.
Mike
prev parent reply other threads:[~2001-11-06 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 2:55 Dirty Page cache in 2.4 David Chow
2001-11-06 3:04 ` Mike Fedyk [this message]
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=20011105190417.A665@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidchow@rcn.com.hk \
--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;
as well as URLs for NNTP newsgroup(s).