From: liyu <liyu@ccoss.com.cn>
To: LKML <linux-kernel@vger.kernel.org>, Linux-MM <linux-mm@kvack.org>
Subject: [Question] How to understand Clock-Pro algorithm?
Date: Tue, 20 Sep 2005 11:11:17 +0800 [thread overview]
Message-ID: <432F7DD5.6050204@ccoss.com.cn> (raw)
Hi, every in LKML/linux-mm:
I have been read CLOCK-Pro paper since last week, and am going to
write one python demo.
After just read , I think I can understand it, however once I begin
implement it, I
found there are many point that not clear.
First, two important parameters Mc, Mh,
In that paper, it assume total memory size is M. (in number of page)
There is a formula:
M = Mc+Mh.
Mc, number of cold pages in memory,
Mh, number of hot pages in memory.
So, in clock list, we can keep track 2M page metadatas at most, we
may include M
non-resident pages.
In '4.3 operationes on searching vicim pages' , the authors said
"we keep track of the number of non-resident cold pages, Once the number
exceeds m the memory size in number of pages. we terminted the test
period of
the cold page pointed to by HAND-test."
My question is out:As this paper words, the number of cold page is
total of resident cold pages
and non-resident pages. It's the seem number of non-resident cold pages
can not beyond M at all!
I also have more questions on CLOCK-Pro. but this question is most
doublt for me.
Any clear word is welcome. thank in advanced.
I suppose experience is more important than theory in
page-replacement field, is it right?
liyu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2005-09-20 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 3:11 liyu [this message]
2005-09-20 4:01 ` Song Jiang
2005-09-20 5:02 ` liyu
2005-09-20 5:16 ` Song Jiang
2005-09-20 5:28 ` liyu
2005-09-20 6:01 ` liyu
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=432F7DD5.6050204@ccoss.com.cn \
--to=liyu@ccoss.com.cn \
--cc=linux-kernel@vger.kernel.org \
--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