From: "Scott F. H. Kaplan" <sfkaplan@cs.amherst.edu>
To: Rik van Riel <riel@redhat.com>
Cc: Nitin Gupta <nitingupta.mail@gmail.com>, linux-mm@kvack.org
Subject: Re: why its dead now?
Date: Sat, 19 Nov 2005 21:24:10 -0500 [thread overview]
Message-ID: <20051120022410.GA5999@sirius.cs.amherst.edu> (raw)
In-Reply-To: <Pine.LNX.4.63.0511191829100.13937@cuia.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Rik,
On Sat, Nov 19, 2005 at 06:30:01PM -0500, Rik van Riel wrote:
> On Tue, 15 Nov 2005, Scott F. H. Kaplan wrote:
>
> > For completely different purposes, we have a 2.4.x kernel that
> > maintains this history efficiently. If you (or anyone else) are
> > interested at some point in porting this reference-pattern-gathering
> > code forward to the 2.6.x line,
>
> Marcelo already did some work on that:
>
> http://linux-mm.org/PageTrace
Nope. Marcelo's work on reference trace collection overlaps with
other work I've done (kVMTrace), but I'm referring to something
completely different.
Specifically, I'm talking about gathering LRU miss histograms
(A.K.A. ``miss rate curves'') online in the kernel. A paper in ASPLOS
2004 presented this idea, as did we in an ISMM 2004 paper on
automatically resizing garbage collectors. We have a kernel with much
lower overhead than the ASPLOS paper presents.
These histograms can be used to perform various kinds of cost/benefit
calculations for current reference patterns. In this case, it could
be used to implement the method I presented in a USENIX 1999 paper for
dynamically adaptic compressed cache sizes. It's a mechanism that
would be difficult to trick into maladaptivity.
Scott
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-11-20 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 18:35 Nitin Gupta
2005-11-14 19:58 ` Rodrigo S de Castro
2005-11-15 3:28 ` Rik van Riel
2005-11-15 14:27 ` Scott F. H. Kaplan
2005-11-19 23:30 ` Rik van Riel
2005-11-20 2:24 ` Scott F. H. Kaplan [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=20051120022410.GA5999@sirius.cs.amherst.edu \
--to=sfkaplan@cs.amherst.edu \
--cc=linux-mm@kvack.org \
--cc=nitingupta.mail@gmail.com \
--cc=riel@redhat.com \
/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