From: Chris Mason <chris.mason@oracle.com>
To: David Nicol <davidnicol@gmail.com>
Cc: Goffredo Baroncelli <kreijack@gmail.com>,
linux-btrfs@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: [RFC] proposal for a btrfs filesystem layout
Date: Fri, 20 Nov 2009 14:50:17 -0500 [thread overview]
Message-ID: <20091120195017.GZ3110@think> (raw)
In-Reply-To: <934f64a20911201124q2a42fddek87d3f8fe864b3c41@mail.gmail.com>
On Fri, Nov 20, 2009 at 01:24:42PM -0600, David Nicol wrote:
> On Fri, Nov 20, 2009 at 12:50 PM, Goffredo Baroncelli
> <kreijack@gmail.com> wrote:
>
> > Any comments ?
> > BR
> > G.Baroncelli
>
>
> since COW semantics require touching directory entries all the way up
> to the root of the subvolume, for transaction-intensive applications
> it would make sense to provide something that works like "mkdir" but
> creates a subvolume that will be mounted at a point rather than a
> simple directory entry. To avoid contention serializing updates to the
> root directory. Is something like that already in place?
COW semantics require touching btree nodes all the way up to the root of
the btree, but this is different from the directory. Directories are
stored in the btree, but you won't have to touch more than 8 or so btree
levels regardless of how deep your directory tree is.
-chris
next prev parent reply other threads:[~2009-11-20 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 18:50 [RFC] proposal for a btrfs filesystem layout Goffredo Baroncelli
2009-11-20 19:24 ` David Nicol
2009-11-20 19:50 ` Chris Mason [this message]
2009-11-20 20:05 ` David Nicol
2009-11-24 1:26 ` Chris Mason
2009-11-20 19:54 ` Chris Mason
2009-11-20 23:31 ` Goffredo Baroncelli
2009-11-24 1:27 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 18:27 Goffredo Baroncelli
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=20091120195017.GZ3110@think \
--to=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=davidnicol@gmail.com \
--cc=kreijack@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