From: Lars Marowsky-Bree <lmb@suse.de>
To: Neil Brown <neilb@suse.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: lars.ellenberg@linbit.com, arjan@infradead.org,
jens.axboe@oracle.com, 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
Date: Fri, 25 Sep 2009 11:59:08 +0200 [thread overview]
Message-ID: <20090925095908.GC28951@suse.de> (raw)
In-Reply-To: <19132.21708.867658.970822@notabene.brown>
On 2009-09-25T15:27:40, Neil Brown <neilb@suse.de> wrote:
> > Enterprise vendors don't pick up the latest kernel. So I think that we
> > need more.
Enterprise kernel providers tend to accept the burden of supporting
their enterprise releases. While I appreciate the thought from the
community, I think the enterprise kernels already including drbd would
be extremely happy to see it officially included.
> I don't really follow your logic, but that isn't important. I think
> that we need to be open to deprecating old ABIs, particularly when the
> ABI is largely used by just one or two programs or libraries. This is
> the case for md/dm/drbd and similar devices.
It is even one step beyond this here. The additional ABI effort is
raised as an objection to merging drbd, and the drbd developers and user
community is offering to depreciate it within a reasonable timeframe of
a better ABI existing (since this will be hidden in the user-space
tools), if this means that it can be merged earlier.
This is quite different from an ABI which is expected to be stable and
remain forever (even if it was just an implicit user assumption); the
expectations are set accordingly from day 0, and thus should not be a
hurdle to acceptance.
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-25 10:01 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
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 [this message]
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=20090925095908.GC28951@suse.de \
--to=lmb@suse.de \
--cc=James.Bottomley@suse.de \
--cc=Mauelshagen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.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