From: Heinz Mauelshagen <heinzm@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH v3 0/4] dm-replicator: introduce new remote replication target
Date: Wed, 09 Dec 2009 19:03:08 +0100 [thread overview]
Message-ID: <1260381788.9639.115.camel@o> (raw)
In-Reply-To: <20091209103941.GA920@infradead.org>
On Wed, 2009-12-09 at 05:39 -0500, Christoph Hellwig wrote:
> On Tue, Dec 08, 2009 at 12:42:27PM -0600, James Bottomley wrote:
> > Could I just echo Lars' statement. With the upstream inclusion of drbd,
> > dm-replicator becomes a *third* replication system asking to be in
> > kernel. It is definitely a kernel policy question of whether we want
> > three separate replicators, and so should be Cc'd to lkml so that people
> > interested in that can weigh in.
>
> And unliley the previous two this one actually offers the benefit of
> beeing integrated with our major block device management framework.
Yes.
Plus it removes the 3 site limitation (2048 technical limit) and offers
consistent multi-device replication.
>
> Interesting that the question comes up now after I was shot down for it
> in the drbd discussion.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2009-12-09 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 16:05 [PATCH v3 0/4] dm-replicator: introduce new remote replication target heinzm
2009-12-01 16:05 ` [PATCH v3 1/4] dm-replicator: documentation and module registry heinzm
2009-12-01 16:05 ` [PATCH v3 2/4] dm-replicator: replication log and site link handler interfaces and main replicator module heinzm
2009-12-01 16:05 ` [PATCH v3 3/4] dm-replicator: ringbuffer replication log handler heinzm
2009-12-01 16:05 ` [PATCH v3 4/4] dm-replicator: blockdev site link handler heinzm
2009-12-01 16:41 ` [PATCH v3 0/4] dm-replicator: introduce new remote replication target Lars Marowsky-Bree
2009-12-01 17:18 ` Heinz Mauelshagen
2009-12-08 18:42 ` James Bottomley
2009-12-09 10:39 ` Christoph Hellwig
2009-12-09 18:03 ` Heinz Mauelshagen [this message]
2009-12-09 18:14 ` James Bottomley
2009-12-09 18:12 ` James Bottomley
2009-12-09 18:38 ` Mike Snitzer
2009-12-09 18:46 ` James Bottomley
2009-12-09 19:14 ` Mike Snitzer
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=1260381788.9639.115.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