[Drbd-dev] [GIT PULL] DRBD for 2.6.32
kyle at moffetthome.net
Tue Sep 22 02:51:32 CEST 2009
On Mon, Sep 21, 2009 at 18:27, FUJITA Tomonori
<fujita.tomonori at lab.ntt.co.jp> wrote:
> On Mon, 21 Sep 2009 18:53:21 +0200 Lars Ellenberg <lars.ellenberg at linbit.com> wrote:
>> That's not what I meant, of course that is and needs to be stable.
>> Sorry, I exagerated to make a point.
>> Point was:
>> mdadm configured md.
>> dmsetup configured dm.
>> drbdsetup configure drbd.
>> If and when "something" is done to "unify" things on the implementation
>> level, it is likely to also unify the "kernel<->userspace" configuration
>> 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.
> We plan to unify the multiple device frameworks, but the unified
> framework must support the all existing ABIs.
> So adding another 'drbd' ABI hurts us.
One major issue for me personally (and I don't think its been mentioned enough):
There is a *VAST* existing user-base for DRBD. Basically every vendor
builds the modules for their kernels, ships the userspace tools, etc.
*Regardless* of when or how it gets merged, the existing user-base
will need kernel support for the existing tools.
You have to realize that this project is NOT a new one, it's been
around quite a decent number of years (since kernel 2.2-ish). Yes,
the ABI is unique and has its warts, but there are a lot of things
that depend on it.
Think of it (in concept) like merging mainline support for an
architecture that has been forward-ported as patches since 2.2. If
the architecture was a simple embedded-only one (like a few recent
ones have been), then you might just say "hell with it, everybody
needs to rebuild libc and the world". That doesn't seem to be the
case with an enterprise-supported distributed block device.
IMHO, we should treat the kernel<=>userspace ABI as fixed... it's an
existing wart that will need to be supported for a while. The
benefits of getting the stable and long-out-of-tree drbd modules into
the mainline kernel will far outweigh the pain of having to maintain
the existing ABI.
To put it another way: Would you really keep a stable SCSI raid
driver for existing hardware out of mainline by claiming they need to
write a new raid-management abstraction first? If not, then why the
pushback on DRBD?
More information about the drbd-dev