Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752255AbZIWXFY (ORCPT ); Wed, 23 Sep 2009 19:05:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751179AbZIWXFW (ORCPT ); Wed, 23 Sep 2009 19:05:22 -0400 Received: from cantor.suse.de ([195.135.220.2]:56556 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbZIWXFV (ORCPT ); Wed, 23 Sep 2009 19:05:21 -0400 From: Neil Brown To: FUJITA Tomonori Date: Thu, 24 Sep 2009 09:06:15 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19130.43495.807916.962040@notabene.brown> Cc: lmb@suse.de, lars.ellenberg@linbit.com, arjan@infradead.org, jens.axboe@oracle.com, neilb@suse.de, hch@infradead.org, James.Bottomley@suse.de, 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, Mauelshagen@redhat.com Subject: Re: [GIT PULL] DRBD for 2.6.32 In-Reply-To: message from FUJITA Tomonori on Wednesday September 23 References: <20090921165321.GJ8072@barkeeper1-xen.linbit> <20090922072617U.fujita.tomonori@lab.ntt.co.jp> <20090922062034.GE22732@suse.de> <20090923203531C.fujita.tomonori@lab.ntt.co.jp> X-Mailer: VM 7.19 under Emacs 21.4.1 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2283 Lines: 55 On Wednesday September 23, fujita.tomonori@lab.ntt.co.jp wrote: > On Tue, 22 Sep 2009 08:20:34 +0200 > Lars Marowsky-Bree wrote: > > > On 2009-09-22T07:27:21, FUJITA Tomonori wrote: > > > > > > If it happens, once that happens, that _will_ be an ABI break. > > > > > > You misunderstand the raid unification. > > > > > > We will not unify the kernel<->userspace configuration interface > > > because we can't break the kernel<->userspace ABI. > > > > I disagree here. Who says we can't over time, and with due notice? > > > > For sure, the new ABI needs to co-exist with the old ones for a while, > > until it is proven and fully complete, but then, why can't the old one > > be marked as depreciated and phased out over 1-2 years time? > > Let me know If you find a Linux storage developer who say, "Yeah, we > can remove the md ABI over 1-2 years time after the raid unification". I would have said 3-5 years, that being about the time frame for enterprise releases, and it would be best if every enterprise vendor got to have a release that supported both the old and the new interface. But I don't have a problem with migrating to a better ABI is we actually had a better ABI. > > Seems that you have a very different idea from other kernel developers > about the stable ABI. CONFIG_SYSFS_DEPRECATED_V2 seems to suggest that other kernel developers understand that we sometimes make mistakes and need to deprecate them. However I think this is all very premature as there is even a coherent proposal for what unification might look like, let alone broad agreement or implementation. I would *much* rather we spent our energies debating that than debating whether or not DRBD should get merged.... Maybe would should only accept votes on "Should DRBD get merged" from people provide constructive input to the question "what would a unified virtual block device model look like". > > Improving the existing framework is a proper approach. Yes. So let's do it. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/