From: Lars Marowsky-Bree <lmb@suse.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>, jens.axboe@oracle.com
Cc: neilb@suse.de, hch@infradead.org, James.Bottomley@suse.de,
lars.ellenberg@linbit.com, linux-kernel@vger.kernel.org,
drbd-dev@lists.linbit.com, akpm@linux-foundation.org,
bart.vanassche@gmail.com, davej@redhat.com, gregkh@suse.de,
kosaki.motohiro@jp.fujitsu.com, kyle@moffetthome.net,
torvalds@linux-foundation.org, nab@linux-iscsi.org,
knikanth@suse.de, philipp.reisner@linbit.com, sam@ravnborg.org
Subject: Re: [GIT PULL] DRBD for 2.6.32
Date: Sun, 20 Sep 2009 00:02:32 +0200 [thread overview]
Message-ID: <20090919220232.GB31849@suse.de> (raw)
In-Reply-To: <20090919141334N.fujita.tomonori@lab.ntt.co.jp>
On 2009-09-19T14:14:30, FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> I guess that Christoph is worry about adding another user interface
> for kinda device management; once we merge this, we can't fix it (for
> the raid unification).
Why can't it be fixed?
Either
a) there's going to be a transition period during which the "old"
interface is supported but depreciated and scheduled to be removed (all
driving the new unified same back-end),
or b) there's going to be a new kernel which requires new user-space
tools sharp.
In either case, dm/md are affected by this, so a third interface doesn't
really make much difference. The refactoring needs to happen in the
back-end anyway, and that actually becomes easier when all concurrent
implementations are present and can be reworked at the same time.
> BTW, DM already has something like drbd? I thought that there is a
> talk about that new target at LinuxCon.
dm-replicator is nowhere near as usable as DRBD, and not upstream yet
either. (Further, it's another independent implementation, pursued
instead of unifying any of the existing ones or helping to merge drbd -
don't get me started on my thoughts of that.)
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
next prev parent reply other threads:[~2009-09-19 22:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 14:45 [GIT PULL] DRBD for 2.6.32 Philipp Reisner
2009-09-15 23:19 ` Christoph Hellwig
2009-09-16 8:33 ` Philipp Reisner
2009-09-17 8:12 ` Lars Ellenberg
2009-09-17 16:02 ` James Bottomley
2009-09-17 16:11 ` Christoph Hellwig
2009-09-18 3:32 ` Neil Brown
2009-09-18 20:08 ` Jens Axboe
2009-09-19 5:14 ` FUJITA Tomonori
2009-09-19 22:02 ` Lars Marowsky-Bree [this message]
2009-09-19 23:56 ` Dan Williams
2009-09-21 13:39 ` FUJITA Tomonori
2009-09-21 14:43 ` Lars Ellenberg
2009-09-21 14:52 ` Arjan van de Ven
2009-09-21 16:53 ` Lars Ellenberg
2009-09-21 22:27 ` FUJITA Tomonori
2009-09-22 0:51 ` Kyle Moffett
2009-09-23 11:27 ` FUJITA Tomonori
2009-09-23 11:57 ` Christoph Hellwig
2009-09-23 14:01 ` Kyle Moffett
2009-09-23 23:21 ` FUJITA Tomonori
2009-09-22 6:20 ` Lars Marowsky-Bree
2009-09-23 11:36 ` FUJITA Tomonori
2009-09-23 23:06 ` Neil Brown
2009-09-23 23:37 ` FUJITA Tomonori
2009-09-25 5:27 ` Neil Brown
2009-09-25 9:59 ` Lars Marowsky-Bree
2009-09-21 14:55 ` [Drbd-dev] " Lars Ellenberg
2009-09-22 5:37 ` Heinz Mauelshagen
2009-09-17 8:50 ` Lars Marowsky-Bree
2009-09-16 0:46 ` KOSAKI Motohiro
2009-09-16 9:19 ` Philipp Reisner
-- strict thread matches above, loose matches on Subject: below --
2009-09-17 18:52 devzero
2009-09-23 19:10 devzero
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=20090919220232.GB31849@suse.de \
--to=lmb@suse.de \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=davej@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kyle@moffetthome.net \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=neilb@suse.de \
--cc=philipp.reisner@linbit.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/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