All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Lars Ellenberg <lars.ellenberg@linbit.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Bart Van Assche <bart.vanassche@gmail.com>,
	Dave Jones <davej@redhat.com>, Greg KH <gregkh@suse.de>,
	Jens Axboe <jens.axboe@oracle.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	Lars Marowsky-Bree <lmb@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Neil Brown <neilb@suse.de>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Nikanth Karthikesan <knikanth@suse.de>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [GIT PULL] DRBD for 2.6.32
Date: Thu, 17 Sep 2009 12:11:09 -0400	[thread overview]
Message-ID: <20090917161108.GA3361@infradead.org> (raw)
In-Reply-To: <1253203365.7845.14.camel@mulgrave.site>

On Thu, Sep 17, 2009 at 10:02:45AM -0600, James Bottomley wrote:
> So I think Christoph's NAK is rooted in the fact that we have a
> proliferation of in-kernel RAID implementations and he's trying to
> reunify them all again.
> 
> As part of the review, reusing the kernel RAID (and actually logging)
> logic did come up and you added it to your todo list.  Perhaps expanding
> on the status of that would help, since what's being looked for is that
> you're not adding more work to the RAID reunification effort and that
> you do have a plan and preferably a time frame for coming into sync with
> it.

Yes.  RDBD has spend tons of time out of tree, and if they want to put
it in now I think requiring them to do their homework is a good idea.

Note that the in-kernel raid implementation is just a rather small part
of this, what's much more important is the user interface.  A big part
of raid unification is that we can support on proper interface to deal
with raid vs volume management, and DRBD adds another totally
incompatible one to that.  We'd be much better off adding the drbd in
the write protocol (at least the most recent version) to DM instead of
adding another big chunk of framework.


  reply	other threads:[~2009-09-17 16:11 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 [this message]
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
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
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=20090917161108.GA3361@infradead.org \
    --to=hch@infradead.org \
    --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=gregkh@suse.de \
    --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=lmb@suse.de \
    --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 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.