From: Andreas Dilger <adilger@clusterfs.com>
To: Kalpak Shah <kalpak@linsyssoft.com>
Cc: Karuna sagar K <karunasagark@gmail.com>, Amit Gud <gud@ksu.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ChunkFS - measuring cross-chunk references
Date: Mon, 23 Apr 2007 14:53:33 -0600 [thread overview]
Message-ID: <20070423205333.GZ5967@schatzie.adilger.int> (raw)
In-Reply-To: <1177320876.23226.7.camel@garfield>
On Apr 23, 2007 15:04 +0530, Kalpak Shah wrote:
> On Mon, 2007-04-23 at 12:49 +0530, Karuna sagar K wrote:
> > The tool estimates the cross-chunk references from an extt2/3 file
> > system. It considers a block group as one chunk and calcuates how many
> > block groups does a file span across. So, the block group size gives
> > the estimate of chunk size.
> >
> > The file systems were aged for about 3-4 months on a developers laptop.
>
> With a blocksize of 4KB, a block group would be 128 MB. In the original
> Chunkfs paper, Valh had mentioned 1GB chunks and I believe it will be
> possible to use 2GB, 4GB or 8GB chunks in the future. As the chunk size
> increases the number of cross-chunk references will reduce and hence it
> might be a good idea to present these statistics considering different
> chunk sizes starting from 512MB upto 2GB.
Also, given that cross-chunk references will be more expensive to fix, I
can imagine the allocation policy for chunkfs will try to avoid this if
possible, further reducing the number of cross-chunk inodes. I guess it
should be more clear whether the cross-chunk references are due to inode
block references, or because of e.g. directories referencing inodes in
another chunk.
Also, is it considered a cross-chunk reference if a directory entry is
referencing an inode in another group? Should there be a continuation
inode in the local group, or is the directory entry itself enough?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-04-23 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 20:35 ChunkFS - measuring cross-chunk references Karuna sagar K
2007-04-22 16:27 ` Amit Gud
2007-04-23 7:19 ` Karuna sagar K
2007-04-23 9:34 ` Kalpak Shah
2007-04-23 20:53 ` Andreas Dilger [this message]
2007-04-24 0:13 ` Theodore Tso
2007-04-24 1:02 ` Arjan van de Ven
2007-04-24 1:24 ` Amit Gud
2007-04-24 1:38 ` Amit Gud
2007-04-24 15:07 ` Theodore Tso
2007-04-25 0:17 ` Karuna sagar K
2007-04-25 0:20 ` Karuna sagar K
2007-04-25 10:23 ` Suparna Bhattacharya
2007-05-19 22:49 ` Karuna sagar K
2007-05-07 5:18 ` Valerie Henson
2007-05-07 1:09 ` Valerie Henson
2007-05-07 1:09 ` Valerie Henson
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=20070423205333.GZ5967@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=gud@ksu.edu \
--cc=kalpak@linsyssoft.com \
--cc=karunasagark@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).