From: Chris Mason <chris.mason@oracle.com>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] initial version of reference cache
Date: Tue, 29 Jul 2008 00:25:25 +0000 [thread overview]
Message-ID: <1217291125.7572.110.camel@think.oraclecorp.com> (raw)
In-Reply-To: <f058a9c30807280953k6cac85a1i9bc10bf41cdb23d7@mail.gmail.com>
On Mon, 2008-07-28 at 17:53 +0100, Miguel Sousa Filipe wrote:
> Hi all,
>
> On Mon, Jul 28, 2008 at 4:09 PM, Chris Mason <chris.mason@oracle.com> wrote:
> > Yan and I are hammering this out a little, I've attached my current
> > patches.
> >
> > I was seeing cache misses after long stress runs, which I think is
> > coming from references on the higher levels of the tree making us skip
> > some leaves while dropping the transaction that added them.
> >
> > My new version using a single cache per root, and should avoid these
> > misses.
>
> Just curious, what is the cache size and or eviction policy?
> Is it LFU or LRU, fifo, something custom? Would ARC be a good policy
> for this purpose?
>
Since this is a cache of the extents pointers in a COW block, things are
only written once, and these items are only read once most of the time.
So, we don't need anything fancy, just a direct access list that we can
use to pull off really old things.
In this case, it is just a list head.
-chris
next prev parent reply other threads:[~2008-07-29 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 19:29 [PATCH] initial version of reference cache Yan Zheng
2008-07-25 23:38 ` Chris Mason
2008-07-26 14:26 ` Yan Zheng
2008-07-28 15:09 ` Chris Mason
[not found] ` <f058a9c30807280952m2386aad4pa8a08ffaf930c370@mail.gmail.com>
2008-07-28 16:53 ` Miguel Sousa Filipe
2008-07-29 0:25 ` Chris Mason [this message]
[not found] ` <4891C236.3000604@redhat.com>
2008-07-31 14:11 ` still see locking issues Chris Mason
2008-07-31 14:37 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2008-07-25 20:57 [PATCH] initial version of reference cache Yan Zheng
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=1217291125.7572.110.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.filipe@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.