From: Andi Kleen <andi@firstfloor.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 Workshop Draft Minutes
Date: Tue, 24 Apr 2012 05:22:35 -0700 [thread overview]
Message-ID: <m2397tnwtw.fsf@firstfloor.org> (raw)
In-Reply-To: <E1SMKmr-0002jQ-4N@tytso-glaptop.cam.corp.google.com> (Theodore Ts'o's message of "Mon, 23 Apr 2012 11:02:45 -0400")
"Theodore Ts'o" <tytso@mit.edu> writes:
> address why Tao Bao is interested in changing the extent format to
> break the 2**15 block extent length limitation. (There are other
> advantages that would accrue to creating a V2 extent tree format, such
It would be good to reserve some space for data checksums in future
extent formats.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2012-04-24 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 15:02 Ext4 Workshop Draft Minutes Theodore Ts'o
2012-04-24 12:22 ` Andi Kleen [this message]
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=m2397tnwtw.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-ext4@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.