From: Vivek Goyal <vgoyal@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Device mapper target driver for Write tracking or Write split
Date: Fri, 9 Jan 2015 09:23:13 -0500 [thread overview]
Message-ID: <20150109142313.GB24745@redhat.com> (raw)
In-Reply-To: <e1aa69e2-7af2-4003-8b8c-5a2b6987a3e2@default>
On Thu, Jan 08, 2015 at 09:23:21PM -0800, Suresh Babu Kandukuru wrote:
> Hi List,
>
>
>
> I am mainly looking at write tracking Device Mapper device . Do we have any device mapper target driver for write tacking or write splitting ?. or any work happening on this to leverage ?. Please kindly share any web links or pointers on this . Thanks in advance .
>
Hi Suresh,
Could you give more details. What is write tracking/splitting and what
are you planning to do with that.
Thanks
Vivek
next prev parent reply other threads:[~2015-01-09 14:23 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 [this message]
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
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=20150109142313.GB24745@redhat.com \
--to=vgoyal@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 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.