From: Andreas Dilger <adilger@clusterfs.com>
To: sho@tnes.nec.co.jp
Cc: cmm@us.ibm.com, jitendra@linsyssoft.com,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
tytso@mit.edu, sct@redhat.com
Subject: Re: [UPDATE][12/24]ext3 enlarge blocksize
Date: Tue, 30 May 2006 13:12:41 -0600 [thread overview]
Message-ID: <20060530191241.GJ5964@schatzie.adilger.int> (raw)
In-Reply-To: <20060530212434sho@rifu.tnes.nec.co.jp>
On May 30, 2006 21:24 +0900, sho@tnes.nec.co.jp wrote:
> On May 26, 2006, Andreas wrote:
> > At least part of this patch can be included into the patch series that
> > Mingming has posted to allow larger block sizes on architectures that
> > support it. This doesn't need a separate COMPAT flag itself, since
> > older kernels will already refuse to mount a filesystem with
> > large blocks.
>
> Do you mention block size?
Yes, it just seemed confusing to be including these two items in the
same patch. I was trying to indicate that the 64k block support should
be submitted to Mingming as a standalone patch atop her patch series,
which is the one that will be submitted for kernel inclusion.
> I don't use the COMPAT flag for large block size, but for >2G blocks.
Agreed. However, there will be a different COMPAT flag for large
filesystems introduced as part of the other 48-bit ext3 changes.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-05-30 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 12:24 sho
2006-05-30 19:12 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-25 12:49 sho
2006-05-26 12:00 ` Andreas Dilger
2006-06-05 13:13 ` Johann Lombardi
2006-06-05 20:13 ` 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=20060530191241.GJ5964@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jitendra@linsyssoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=sho@tnes.nec.co.jp \
--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
all inboxes | Powered by JetHome®