linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: thornber@redhat.com
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How does LVM-Cache work?
Date: Thu, 28 Feb 2013 09:58:23 +0000	[thread overview]
Message-ID: <20130228095822.GA3013@raspberrypi> (raw)
In-Reply-To: <CAEZ+n-gv=9Gdg8b3xKW5JraNVvRhc3fqiYUvL+6vt4Wrdda02A@mail.gmail.com>

On Wed, Feb 27, 2013 at 03:30:47PM -0300, Leo Antonio wrote:
> Thanks for answers.
> 
> 
> I take a look in dm-cache-target, I really dont knew this project.
> 
> Joe, what is the best way to continue this discussion?
> 
> Do you have some documentation besides what is into kernel source, like
> Papers, Architecture Projects etc?
> What is the best way to start to understand this?

The best place to start is by reading
Documentation/device-mapper/cache.txt and trying it out a bit.  Then
read drivers/md/dm-cache-policy.h which defines the interface that
policies use.  Finally look at dm-cache-policy-mq.c (multiqueue
policy).  This should give you a good idea of the responsibilities of
a policy.

An alternative project would be creating a framework for assessing
cache policies.  Not just providing a range of different cache loads
(though that is a big important part), but also providing feedback to
the policy developer as to how their policy could be improved.  I'd like
to see a tool that calculates the optimimum series of
promotions/demotions for a given io load and so comes up with a
theoretical 'best' performance.

- Joe

      parent reply	other threads:[~2013-02-28  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 18:44 [linux-lvm] How does LVM-Cache work? Leo Antonio
2013-02-27  9:46 ` Zdenek Kabelac
2013-02-27 10:04 ` thornber
2013-02-27 18:30   ` Leo Antonio
2013-02-28  8:42     ` Greg Zapp
2013-02-28  9:58     ` thornber [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=20130228095822.GA3013@raspberrypi \
    --to=thornber@redhat.com \
    --cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).