All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: jeffschroeder@computer.org, linux-btrfs@vger.kernel.org
Subject: Re: HP opensourced advfs from tru64 and what it means for btrfs
Date: Mon, 23 Jun 2008 14:59:12 -0400	[thread overview]
Message-ID: <1214247552.10187.594.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20080623184532.GA27013@2ka.mipt.ru>

On Mon, 2008-06-23 at 22:45 +0400, Evgeniy Polyakov wrote:
> On Mon, Jun 23, 2008 at 02:21:09PM -0400, Chris Mason (chris.mason@oracle.com) wrote:
> > > 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.
> > 
> > In general, the rules that make filesystems go haven't changed in a long
> > time.   Disks are slow, ram is faster, and cpu is both infinitely fast
> > and important to share with other things running on the hardware.
> 
> I believe if things are that simple, you would not start btrfs? :)
> 

Grin, just because everyone knows the rules doesn't mean you shouldn't
try playing.  SSD does change the dynamics as well in ways that I think
btrfs is best suited to handle.

The idea is that well established filesystems can teach us quite a lot
about layout, and about the optimizations that were added in response to
customer demand.  Having the code to these optimizations is very useful.

-chris



  reply	other threads:[~2008-06-23 18:59 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
2008-06-23 18:21   ` Chris Mason
2008-06-23 18:45     ` Evgeniy Polyakov
2008-06-23 18:59       ` Chris Mason [this message]
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=1214247552.10187.594.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=jeffschroeder@computer.org \
    --cc=johnpol@2ka.mipt.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.