From: Nikita Danilov <nikita@clusterfs.com>
To: Valerie Henson <val_henson@linux.intel.com>
Cc: Matt Mackall <mpm@selenic.com>, Theodore Tso <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] TileFS - a proposal for scalable integrity checking
Date: Wed, 9 May 2007 23:19:50 +0400 [thread overview]
Message-ID: <17986.7894.913448.214067@gargle.gargle.HOWL> (raw)
In-Reply-To: <20070509185631.GA18778@nifty>
Valerie Henson writes:
[...]
>
> You're right about needing to read the equivalent data-structure - for
> other reasons, each continuation inode will need an easily accessible
> list of byte ranges covered by that inode. (Sounds like, hey,
> extents!) The important part is that you don't have go walk all the
I see. I was under impression that idea was to use indirect blocks
themselves as that data-structure, e.g., block number 0 to mark holes,
block number 1 to mark "block not in this continuation", and all other
block numbers for real blocks.
> indirect blocks or check your bitmap.
>
> -VAL
Nikita.
next prev parent reply other threads:[~2007-05-09 19:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 22:05 [RFC] TileFS - a proposal for scalable integrity checking Matt Mackall
2007-04-29 12:21 ` Jörn Engel
2007-04-29 12:57 ` Matt Mackall
2007-04-29 15:47 ` Jörn Engel
2007-05-09 5:56 ` Valerie Henson
2007-05-09 10:12 ` Jörn Engel
2007-04-29 15:58 ` Jörn Engel
2007-04-29 16:24 ` Matt Mackall
2007-04-29 16:34 ` Andi Kleen
2007-04-29 16:05 ` Jörn Engel
2007-04-29 16:09 ` Matt Mackall
2007-04-29 23:23 ` Theodore Tso
2007-04-30 1:40 ` Matt Mackall
2007-04-30 17:26 ` Theodore Tso
2007-04-30 17:59 ` Matt Mackall
2007-05-02 13:18 ` Jörn Engel
2007-05-02 13:32 ` Jörn Engel
2007-05-02 15:37 ` Matt Mackall
2007-05-02 16:35 ` Jörn Engel
2007-05-09 7:56 ` Valerie Henson
2007-05-09 11:16 ` Nikita Danilov
2007-05-09 18:56 ` Valerie Henson
2007-05-09 19:19 ` Nikita Danilov [this message]
2007-05-09 17:06 ` Matt Mackall
2007-05-09 18:59 ` Valerie Henson
2007-05-09 19:51 ` Matt Mackall
2007-05-10 0:03 ` Jörn Engel
2007-05-11 9:46 ` Valerie Henson
2007-05-11 15:55 ` Matt Mackall
2007-05-09 19:01 ` Valerie Henson
2007-05-09 20:05 ` Matt Mackall
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=17986.7894.913448.214067@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=tytso@mit.edu \
--cc=val_henson@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).