From: Alex Elsayed <eternaleye@gmail.com>
To: linux-mm@kvack.org
Subject: Re: [RFC 0/4] cleancache: SSD backed cleancache backend
Date: Thu, 10 Oct 2013 10:24:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20131010T122004-708@post.gmane.org> (raw)
In-Reply-To: <20131009115243.GA1198@thunk.org>
Theodore Ts'o <tytso <at> mit.edu> writes:
<snip>
> If we are to do page-level caching, we really need to change the VM to
> use something like IBM's Adaptive Replacement Cache[1], which allows
> us to track which pages have been more frequently used, so that we
> only cache those pages, as opposed to those that land in the cache
> once and then aren't used again. (Consider what might happen if you
> are using clean cache and then the user does a full backup of the
> system.)
>
> [1] http://en.wikipedia.org/wiki/Adaptive_replacement_cache
<snip>
It's a topic that's come up before, [2] is probably the best resource on the
web right now regarding efforts to change the page-replacement algorithm in
Linux. CAR/CART in particular are rather interesting. Seemingly not much
motion recently, though.
[1] NMF
[2] http://linux-mm.org/AdvancedPageReplacement
--
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 prev parent reply other threads:[~2013-10-10 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 14:14 Shaohua Li
2013-09-26 14:14 ` [RFC 1/4] cleancache: make put_page async possible Shaohua Li
2013-09-26 14:14 ` [RFC 2/4] cleancache: make get_page " Shaohua Li
2013-09-26 14:14 ` [RFC 3/4] cleancache: invalidate cache at dirty page Shaohua Li
2013-09-26 14:14 ` [RFC 4/4] cleancache: SSD backed cleancache backend Shaohua Li
2013-09-26 16:14 ` [RFC 0/4] " Seth Jennings
2013-09-29 9:19 ` Shaohua Li
2013-10-09 11:52 ` Theodore Ts'o
2013-10-10 10:24 ` Alex Elsayed [this message]
2013-10-10 10:38 ` Bob Liu
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=loom.20131010T122004-708@post.gmane.org \
--to=eternaleye@gmail.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