Linux NILFS development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org,
	users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Some nilfs comments
Date: Tue, 23 Dec 2008 15:49:09 -0500	[thread overview]
Message-ID: <1230065349.5908.7.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20081224.022337.30445207.ryusuke-sG5X7nlA6pw@public.gmane.org>

On Wed, 2008-12-24 at 02:23 +0900, Ryusuke Konishi wrote:

> > > Thanks, I've also started to read btrfs.
> > > I'll see it during the Christmas holidays  ;)
> > 
> > Whats your first impression? Want to take over things/ideas? Isn't that a
> > quite different FS structurally since it doesn't have segments? (AFAIK!)
> 
> Yeah, btrfs has flexible and rich volume management layer, so very
> interesting.  The snapshot code and c-tree also look like fun.

The ctree (checksummed btree is really what it stands for) code itself
is pretty basic.  Aside from the checksumming, it is a simple btree with
generation numbers to find the nodes that have changed since a given
transaction.

In terms of interesting/new code that others might want look at, the
btrfs tree logging to do fsync efficiently (tree-log.c) and device
management (volumes.c) are probably the most interesting.

-chris

  parent reply	other threads:[~2008-12-23 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  2:52 Some nilfs comments Chris Mason
     [not found] ` <1229568775.27170.134.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-22  9:07   ` Ryusuke Konishi
     [not found]     ` <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-22 13:01       ` Reinoud Zandijk
     [not found]         ` <20081222130152.GA23725-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-12-23 17:23           ` Ryusuke Konishi
     [not found]             ` <20081224.022337.30445207.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-23 20:49               ` Chris Mason [this message]
2008-12-23  1:47       ` Chris Mason
     [not found]         ` <1229996820.4812.7.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-23 15:57           ` Ryusuke Konishi
2009-01-06 19:55       ` Chris Mason
     [not found]         ` <1231271709.4888.27.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2009-01-07  5:20           ` Ryusuke Konishi
     [not found]             ` <20090107.142009.106620982.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-07 14:16               ` Chris Mason

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=1230065349.5908.7.camel@think.oraclecorp.com \
    --to=chris.mason-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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