From: Jean noel Cordenner <jean-noel.cordenner@bull.net>
To: Peter Staubach <staubach@redhat.com>
Cc: NeilBrown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: i_version changes
Date: Fri, 15 Feb 2008 11:31:50 +0100 [thread overview]
Message-ID: <47B56A16.5040906@bull.net> (raw)
In-Reply-To: <47B4524B.7040008@redhat.com>
Peter Staubach a écrit :
>> Few month ago, I ran a FFSB test on a 2.6.23 kernel enabling or not
>> the i_version flag.
>> http://bullopensource.org/ext4/20071116/ffsb-write.html
>
> This is good information.
>
> A couple of questions -- what is the "-I 256" option used for the ext4
> mkfs?
>
This option force the inode size to 256Bytes instead of 128. The
requirement is to have a 64bits i_version counter, therefore the ext4
inode as to be extended to 256Bytes.
> What was the variance between the results of the 5 runs? Is 2%
> significant or not?
>
I didn't keep the raw results, but they were all very close to the
average (less than 1% of the average).
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" 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:[~2008-02-15 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 7:30 i_version changes Christoph Hellwig
2008-02-12 20:06 ` J. Bruce Fields
2008-02-13 9:25 ` Andreas Dilger
2008-02-13 12:52 ` Christoph Hellwig
2008-02-13 14:07 ` Trond Myklebust
2008-02-13 15:12 ` Andreas Dilger
2008-02-13 20:26 ` J. Bruce Fields
2008-02-13 21:19 ` NeilBrown
2008-02-13 21:32 ` Peter Staubach
2008-02-13 22:06 ` NeilBrown
2008-02-14 14:34 ` Peter Staubach
2008-02-14 8:40 ` Jean noel Cordenner
2008-02-14 14:38 ` Peter Staubach
2008-02-15 10:31 ` Jean noel Cordenner [this message]
2008-02-13 21:36 ` J. Bruce Fields
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=47B56A16.5040906@bull.net \
--to=jean-noel.cordenner@bull.net \
--cc=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=staubach@redhat.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 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.