Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] New Features: write-back cache mode
Date: Tue, 30 Sep 2008 22:02:48 +0200	[thread overview]
Message-ID: <20080930200248.GA30030@racke> (raw)
In-Reply-To: <20080920231938.GA16320@racke>

On Sun, Sep 21, 2008 at 01:19:38AM +0200, Lars Ellenberg wrote:
> On Sat, Sep 20, 2008 at 05:04:44PM -0600, Morey Roof wrote:
> > This is pretty much what I was thinking.  For the btree, generations,  
> > and ref-count a good example to look at is how btrfs (This is the other  
> > project I have started to mess with) works.  The design is very  
> > efficient and I think we could use a very close match for our setup.  I  
> > haven't read the paper you sent yet but will get to that today.
> >
> > Let me know how you would like to start and I can start working a proof  
> > of concept and we can see how to go from there.
> 
> I still think that should be implemented as a
> generic device-mapper write-back target,
> not as part of drbd.

> http://www.acis.ufl.edu/~ming/dmcache/

> maybe you can use that as a starting point,
> and point it to a ram disk as cache?

any news on that?

	Lars

      reply	other threads:[~2008-09-30 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19  5:24 [Drbd-dev] New Features Morey Roof
2008-09-19 15:53 ` Lars Ellenberg
2008-09-19 16:19   ` Morey Roof
2008-09-19 22:13     ` Lars Ellenberg
2008-09-19 22:28       ` Morey Roof
2008-09-20 13:18         ` Lars Ellenberg
2008-09-20 13:48           ` Lars Ellenberg
2008-09-20 23:04             ` Morey Roof
2008-09-20 23:19               ` [Drbd-dev] New Features: write-back cache mode Lars Ellenberg
2008-09-30 20:02                 ` Lars Ellenberg [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=20080930200248.GA30030@racke \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.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