From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: jeffschroeder@computer.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: HP opensourced advfs from tru64 and what it means for btrfs
Date: Mon, 23 Jun 2008 18:50:26 +0400 [thread overview]
Message-ID: <20080623145026.GA13310@2ka.mipt.ru> (raw)
In-Reply-To: <c24352ca0806230737g287de15bv5916d1c7501f06be@mail.gmail.com>
Hi.
On Mon, Jun 23, 2008 at 07:37:32AM -0700, Jeff Schroeder (jeffschroed@gmail.com) wrote:
> http://advfs.sourceforge.net/ HP open sourced the advfs filesystem
> from tru64 Unix today under the gplv2.
...
> Would it make sense to look at using any of the code from this in
> btrfs, or would it be easier to
> re-implement it all over again? Even though filesystems ported from
> other Posix operating systems to Linux (Ever looked at XFS code)
> can be ugly, this might be a way to accelerate btrfs development.
> If nothing else, it might be interesting to see how HP solved problems
> btrfs will soon be solving.
Sure it is interesting as studing anything new, but there is nothing in
advfs which can prevent btrfs from success. Virtually nothing.
Advfs is quite old technology built on top of almost 20 years old ideas
and hardware, while the former can still be (and likely is) valid,
hardware made significant progress. Also transaction log approach can
be very slow in lots of cases. I'm not sure using advfs code is ever
possible in btrfs: they are completely different filesystems, which
share mostly only ideas on what end user may or may not want to have.
Also having own new code is better from lots of viewpoints: from time
spent to write vs time to understand, from understandability of some
internal features and so on.
> Don't drink and derive, alcohol and analysis don't mix.
> http://www.digitalprognosis.com
Depending on analysis type :)
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-06-23 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 14:37 HP opensourced advfs from tru64 and what it means for btrfs Jeff Schroeder
2008-06-23 14:50 ` Evgeniy Polyakov [this message]
2008-06-23 18:21 ` Chris Mason
2008-06-23 18:45 ` Evgeniy Polyakov
2008-06-23 18:59 ` Chris Mason
2008-06-24 13:50 ` Chris Samuel
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=20080623145026.GA13310@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=jeffschroeder@computer.org \
--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