From: Coly Li <i@coly.li>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Andreas Dilger <adilger@whamcloud.com>,
linux-ext4 development <linux-ext4@vger.kernel.org>,
Alex Zhuravlev <bzzz@whamcloud.com>, Tao Ma <tm@tao.ma>,
"hao.bigrat@gmail.com" <hao.bigrat@gmail.com>
Subject: Re: bigalloc and max file size
Date: Sun, 30 Oct 2011 13:37:59 +0800 [thread overview]
Message-ID: <4EACE2B7.9070402@coly.li> (raw)
In-Reply-To: <E0A4425F-9C68-4929-83CD-9B2CA3F87979@mit.edu>
On 2011年10月28日 05:42, Theodore Tso Wrote:
>
> On Oct 27, 2011, at 11:08 AM, Andreas Dilger wrote:
[snip]
> One could argue that I could add a patch which disabled the bigalloc patch, and then make changes in the next merge window, but to be completely honest I have my own selfish reason for not wanting to do that, which is the bigalloc patches have also been integrated into Google's internal kernels already, and changing the bigalloc format without a new flag would make things complicated for me. Given that we decided to lock down the extent leaf format (even though I had wanted to make changes to it, for example to support a full 64-bit block number) in deference to the fact that it was in ClusterFS deployed kernels, there is precedent for taking into account the status of formats used in non-mainline kernels by the original authors of the feature.
>
Hi Ted,
Forgive me if this is out of topic.
In our test, allocating directories W/ bigalloc and W/O inline-data may occupy most of disk space. By now Ext4
inline-data is not merged yet, I just wondering how Google uses bigalloc without inline-data patch set ?
Thanks.
--
Coly Li
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-30 5:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 23:36 bigalloc and max file size Andreas Dilger
2011-10-27 1:05 ` Tao Ma
2011-10-27 6:35 ` Theodore Tso
[not found] ` <EB03FF23-73BC-4FDC-B991-5EB3FEEB8DAE@whamcloud.com>
2011-10-27 11:48 ` Theodore Tso
[not found] ` <97D9C5CC-0F22-4BC7-BDFA-7781D33CA7F3@whamcloud.com>
2011-10-27 21:42 ` Theodore Tso
2011-10-28 3:31 ` Tao Ma
2011-10-31 10:15 ` Theodore Tso
2011-10-31 10:27 ` Tao Ma
2011-10-31 18:53 ` Sunil Mushran
2011-10-31 19:09 ` Andreas Dilger
2011-10-31 20:00 ` Ted Ts'o
2011-11-01 4:06 ` Tao Ma
2011-10-30 5:37 ` Coly Li [this message]
2011-10-30 19:49 ` Theodore Tso
2011-10-31 9:35 ` Coly Li
2011-10-31 10:22 ` Theodore Tso
2011-10-31 16:08 ` Andreas Dilger
2011-10-31 16:22 ` Ted Ts'o
2011-10-31 17:39 ` Coly Li
2011-10-31 19:38 ` Ted Ts'o
2011-11-01 1:10 ` Coly Li
2011-11-01 11:47 ` Theodore Tso
2011-11-01 12:22 ` Coly Li
2011-10-31 16:34 ` Andreas Dilger
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=4EACE2B7.9070402@coly.li \
--to=i@coly.li \
--cc=adilger@whamcloud.com \
--cc=bzzz@whamcloud.com \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
--cc=tytso@MIT.EDU \
/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).