From: Theodore Tso <tytso@mit.edu>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: "Frédéric Bohé" <frederic.bohe@bull.net>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/4] Create the journal in the middle of the filesystem
Date: Thu, 28 Aug 2008 10:36:48 -0400 [thread overview]
Message-ID: <20080828143648.GJ26987@mit.edu> (raw)
In-Reply-To: <48B6AACE.6060103@redhat.com>
On Thu, Aug 28, 2008 at 09:40:30AM -0400, Ric Wheeler wrote:
>
> I can try and test this with my fsync() heavy fs_mark run...
>
Given [1] I have no doubt that you should see a difference between
mke2fs from e2fsprogs 1.41.0 (which will allocate the journal at the
beginning of the filesystem) and the latest tip of e2fsprogs.
It would be interesting to see how measurable the difference is,
though. I'd recommend doing "mke2fs -t ext4dev" using both versions
of mke2fs, and seeing how much the difference it makes.
[1] http://www.usenix.org/events/usenix05/tech/general/full_papers/prabhakaran/prabhakaran_html/main.html#fig-journal-location-withinfs-fix
- Ted
next prev parent reply other threads:[~2008-08-28 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 17:36 Journal file fragmentation Frédéric Bohé
2008-08-27 20:12 ` Jose R. Santos
2008-08-27 21:06 ` Theodore Tso
2008-08-27 21:14 ` [PATCH 1/4] ext2fs_mkjournal(): Don't allocate an extra block to the journal Theodore Ts'o
2008-08-27 21:14 ` [PATCH 2/4] Create the journal in the middle of the filesystem Theodore Ts'o
2008-08-27 21:14 ` [PATCH 3/4] ext2fs_block_iterate2: Add BLOCK_FLAG_APPEND support for extent-based files Theodore Ts'o
2008-08-27 21:14 ` [PATCH 4/4] If the filesystem supports extents create an extent-based journal inode Theodore Ts'o
2008-08-28 9:55 ` [PATCH 2/4] Create the journal in the middle of the filesystem Frédéric Bohé
2008-08-28 13:34 ` Theodore Tso
2008-08-28 13:40 ` Ric Wheeler
2008-08-28 14:36 ` Theodore Tso [this message]
2008-08-28 14:38 ` Ric Wheeler
2008-09-03 14:08 ` Ric Wheeler
2008-08-28 16:16 ` Frédéric Bohé
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=20080828143648.GJ26987@mit.edu \
--to=tytso@mit.edu \
--cc=frederic.bohe@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox