public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs development plans
Date: Mon, 20 Apr 2009 10:39:21 -0700	[thread overview]
Message-ID: <gsj87t$cvu$1@ger.gmane.org> (raw)
In-Reply-To: 2a31deca0904200957v39badd2eu4b26844e78fdcde3@mail.gmail.com

Andrey Kuzmin wrote:

<snip>
> Personally, I don't see any. Porting zfs to Linux will cost (quite)
> some time and effort, but this is peanuts compared to what's needed to
> get btrfs  (no offense meant) to maturity level/feature parity with
> zfs. The only thing that could prevent this is CDDL licensing issues
> and patent claims from NTAP over zfs snapshots  and other features;
> btrfs is free from both.
<snip>

There's one thing you're overlooking: the core kernel developers have 
already stated that ZFS is a "rampant layering violation" and otherwise 
indicated they do not want ZFS in the Linux kernel, whereas BtrFS has
gotten a much more positive response. It may well be that on the /Oracle/ 
side, the political and technical problems with porting ZFS are smaller than 
those with finishing BtrFS, but if the kernel developers wouldn't accept it, 
_any_ money and effort spent on it would be wasted money and effort.



  parent reply	other threads:[~2009-04-20 17:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 14:37 Btrfs development plans Chris Mason
2009-04-20 15:31 ` Tomasz Torcz
2009-04-20 16:10   ` Ahmed Kamal
2009-04-20 16:38     ` Chris Mason
2009-04-21  7:46       ` Stephan von Krawczynski
2009-04-21  8:56         ` Dmitri Nikulin
2009-04-21 15:05           ` ashford
2009-04-20 16:57     ` Andrey Kuzmin
2009-04-20 17:08       ` Gregory Maxwell
2009-04-20 17:18         ` Andrey Kuzmin
2009-04-20 17:20           ` Chris Mason
2009-04-20 17:39       ` Alex Elsayed [this message]
2009-04-21  2:27       ` Eric Anopolsky
2009-05-24 12:13         ` Chris Samuel
2009-04-20 18:42 ` Ric Wheeler

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='gsj87t$cvu$1@ger.gmane.org' \
    --to=eternaleye@gmail.com \
    --cc=linux-btrfs@vger.kernel.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