Linux Device Mapper development
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: dm-devel@redhat.com
Subject: Re: dm-cache module
Date: Wed, 28 Apr 2010 10:21:47 +0200	[thread overview]
Message-ID: <1272442907.2031.79.camel@o> (raw)
In-Reply-To: <4BD7906E.6010602@daevel.fr>

On Wed, 2010-04-28 at 03:33 +0200, Olivier B. wrote:
> On 22/03/2010 16:05, Heinz Mauelshagen wrote:
> > On Sun, 2010-03-21 at 00:56 -0400, Ming Zhao wrote:
> >    
> >> Hi Mike,
> >>
> >> Thank you very much for your advice!
> >>
> >> I can revise dm-cache code and resubmit it as you suggested. I would
> >> also love to know Heinz's progress on his implementation and work with
> >> him if there anything I could contribute.
> >>      
> > Hi all,
> >
> > this is a list of the functions of my dm-hstore
> > device-mapper target implementation:
> >
> > o caches reads and writes keeping persistent state metadata.
> > o writes back in order to enhance streaming performance
> >    on fragmented access pattern.
> > o can run on top of readonly original device
> > o if so, writes back any dirty areas when set readwrite
> >    (useful for tests)
> > o readonly<->  readwrite access changes supported via message interface
> > o initializes metadata for extents in cache in the background
> >    in order to fasten cache construction
> > o supports cache resizing via message interface or constructor
> > o keeps metadata persistent by default
> > o stores CRCs with metadata for integrity checks
> > o stores versions with metadata to support future metadata migration
> >
> > Test features only:
> > o transient cache
> > o cache write through
> >
> >
> > Provides very good performance on SSD cache backing stores.
> >
> > Has been shelved for a while because of other priorities so I need to
> > rebase it to the actual kernel.
> >
> > Regards,
> > Heinz
> >
> >    
> Hi,
> 
> Facebook have just released "FlashCache" : 
> http://github.com/facebook/flashcache
> in the documentation we can read :

> Flashcache is built using the Linux Device Mapper (DM), part of the 
> Linux Storage Stack infrastructure that facilitates building SW-RAID and 
> other components.
> 
> So it's an other implementation of the same concept, no ?

Yes, it looks like it. I'll have a closer look how it differs form mine.

Heinz

> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2010-04-28  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21  0:03 dm-cache module Olivier B.
2010-03-21  3:37 ` Mike Snitzer
2010-03-21 10:35   ` Olivier B.
     [not found]   ` <15606e421003202156n21de56a6n868f84bf737cce51@mail.gmail.com>
2010-03-22 15:05     ` Heinz Mauelshagen
2010-04-28  1:33       ` Olivier B.
2010-04-28  8:21         ` Heinz Mauelshagen [this message]
2010-04-28 14:02           ` Heinz Mauelshagen
2011-06-03 19:16             ` Phillip Susi
2011-06-06 10:06               ` Heinz Mauelshagen
2012-12-11 21:49                 ` Phillip Susi
2012-12-11 21:56                   ` Alasdair G Kergon

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=1272442907.2031.79.camel@o \
    --to=heinzm@redhat.com \
    --cc=dm-devel@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