From: David Chinner <dgc@sgi.com>
To: Michael Nishimoto <miken@agami.com>
Cc: XFS Mailing List <xfs@oss.sgi.com>
Subject: Re: Extent merging past MAXEXTLEN
Date: Mon, 4 Feb 2008 09:52:18 +1100 [thread overview]
Message-ID: <20080203225218.GY155407@sgi.com> (raw)
In-Reply-To: <479E4A52.6000804@agami.com>
On Mon, Jan 28, 2008 at 01:34:10PM -0800, Michael Nishimoto wrote:
> Hi everyone,
>
> Is there a reason to continue limiting extent merges past MAXEXTLEN
> on 64-bit systems?
I don't think 32/64bit issues enter into this - the max extent length is
determined by the filesystem block size (the on disk length is in filesystem
blocks) so by default we are already at byte lengths greater than what fits in
a 32bit variable (i.e. 2^21*2^12 = 2^33).
Basically, MAXEXTLEN defines the number of bits in the length field of the on-disk
extent record when it is packed and so without a on-disk format change, we can't
sanely increase the size of this field. Perhaps we should look at doing this,
but it's going to have to wait until the btree re-factoring code is completed
so we can implement the record format change sanely....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-02-03 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 21:34 Extent merging past MAXEXTLEN Michael Nishimoto
2008-02-03 22:52 ` David Chinner [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=20080203225218.GY155407@sgi.com \
--to=dgc@sgi.com \
--cc=miken@agami.com \
--cc=xfs@oss.sgi.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