From: Zheng Da <zhengda1936@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-mm@kvack.org
Subject: Re: ClockPro in Linux MM
Date: Mon, 12 Mar 2012 13:32:51 -0400 [thread overview]
Message-ID: <CAFLer82Nt7gZm-Sq_F_2q0PYp1bUht0op=PvfMu5BW8YwbBMHw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203121102590.6396@router.home>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
I know the implementation is different. Linux implementation doesn't have
the clock heads.
But I get a feel that the essence is the same except that Linux version
doesn't have non-resident pages.
Da
On Mon, Mar 12, 2012 at 12:04 PM, Christoph Lameter <cl@linux.com> wrote:
> On Mon, 12 Mar 2012, Zheng Da wrote:
>
> > I try to understand the Linux memory management. I was told Linux uses
> > ClockPro to manage page cache
> > and http://linux-mm.org/PageReplacementDesign also says so for file
> pages.
> > But when I read the ClockPro paper,
> > it doesn't look the same. The Linux implementation doesn't have
> > non-resident pages. Other than
> > that, it doesn't have the same test period mentioned in the paper. I
> wonder
> > if the Linux implementation
> > have the same effect as ClockPro. Could anyone confirm Linux is still
> using
> > ClockPro?
>
> That Linux is using Clockpro is news to me. Linux Memory management uses
> some ideas from Clockpro to improve reclaim etc but it does not implement
> ClockPro.
>
>
[-- Attachment #2: Type: text/html, Size: 1501 bytes --]
prev parent reply other threads:[~2012-03-12 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 15:19 Zheng Da
2012-03-12 16:04 ` Christoph Lameter
2012-03-12 17:32 ` Zheng Da [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='CAFLer82Nt7gZm-Sq_F_2q0PYp1bUht0op=PvfMu5BW8YwbBMHw@mail.gmail.com' \
--to=zhengda1936@gmail.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.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