From: Jeff Moyer <jmoyer@redhat.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
jens.axboe@oracle.com, esandeen@redhat.com
Subject: Re: [patch/rft] jbd2: tag journal writes as metadata I/O
Date: Mon, 05 Apr 2010 14:36:07 -0400 [thread overview]
Message-ID: <x49hbnpkaqw.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20100405175205.GA4681@thunk.org> (tytso@mit.edu's message of "Mon, 5 Apr 2010 13:52:05 -0400")
tytso@mit.edu writes:
> On Thu, Apr 01, 2010 at 03:04:54PM -0400, Jeff Moyer wrote:
>>
>> So, I'm submitting this patch for comments and testing. I have a
>> similar patch for jbd that I will submit if folks agree that this is a
>> good idea.
>
> Added to the ext4 patch queue.
>
> What benchmark were you using to test small file writes? This looks
> good to me as well, but we might want to do some extra benchmarking
> just to be sure we're not accidentally introducing a performance
> regression.
iozone showed regressions for write and re-write in runs that include
fsync timings for small files (<8MB). Here's the command line used for
testing:
iozone -az -n 4k -g 2048m -y 1k -q 1m -e
I also ran fs_mark using the following command line:
fs_mark -S 1 -D 100 -N 1000 -d /mnt/test/fs_mark -s 65536 -t 1 -w 4096
I'll let you know if there are any regressions caused by this patch in
any of our other testing.
Cheers,
Jeff
next prev parent reply other threads:[~2010-04-05 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 19:04 [patch/rft] jbd2: tag journal writes as metadata I/O Jeff Moyer
2010-04-01 19:48 ` Jan Kara
2010-04-05 15:24 ` Jeff Moyer
2010-04-05 17:46 ` tytso
2010-04-06 15:20 ` Jan Kara
2010-04-06 18:25 ` Vivek Goyal
2010-04-06 18:45 ` tytso
2010-04-06 19:04 ` Jeff Moyer
2010-04-02 7:00 ` Jens Axboe
2010-04-05 17:52 ` tytso
2010-04-05 18:36 ` Jeff Moyer [this message]
2010-04-05 19:48 ` tytso
2010-04-05 20:34 ` Jeff Moyer
2010-04-05 20:41 ` Jeff Moyer
2010-04-05 21:01 ` tytso
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=x49hbnpkaqw.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=esandeen@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).