All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: vgoyal@redhat.com
Subject: Re: Device mapper target driver for Write tracking or Write split
Date: Fri, 9 Jan 2015 16:59:25 +0000	[thread overview]
Message-ID: <20150109165924.GB17009@localhost.localdomain> (raw)
In-Reply-To: <932defdc-db0a-4f1d-9812-1685199aed3a@default>

On Fri, Jan 09, 2015 at 07:51:08AM -0800, Suresh Babu Kandukuru wrote:
> Bryn, Thanks for quick reply. Below items helps to do mirroring and replication . I am looking for something which  can track writes( device mapper based block level filter driver)   as explained in the below diagram in Linux open source community .

Anything that's doing mirroring or replication (or many other useful
target functions) is going to need to 'track' writes (normally by
copying them and keeping track of the copies in the target).

The device-mapper core provides infrastructure to help with this but if
none of the existing dm targets provide the functionality you need then
you will either need to create one from scratch or extend whatever
current target best matches your needs.

Aside from mentioning CDP and replicating data to another appliance you
haven't really stated what you're trying to do.

Regards,
Bryn.

  reply	other threads:[~2015-01-09 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  5:23 Device mapper target driver for Write tracking or Write split Suresh Babu Kandukuru
2015-01-09 14:23 ` Vivek Goyal
2015-01-09 14:51   ` Suresh Babu Kandukuru
2015-01-09 15:13     ` Bryn M. Reeves
2015-01-09 15:51       ` Suresh Babu Kandukuru
2015-01-09 16:59         ` Bryn M. Reeves [this message]
2015-01-12 10:04           ` Suresh Babu Kandukuru
2015-01-12  9:34         ` Zdenek Kabelac

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=20150109165924.GB17009@localhost.localdomain \
    --to=bmr@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=vgoyal@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 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.