From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
esandeen@redhat.com
Subject: Re: [patch/rft] jbd2: tag journal writes as metadata I/O
Date: Fri, 2 Apr 2010 09:00:02 +0200 [thread overview]
Message-ID: <20100402070001.GY23510@kernel.dk> (raw)
In-Reply-To: <x49iq8b9ep5.fsf@segfault.boston.devel.redhat.com>
On Thu, Apr 01 2010, Jeff Moyer wrote:
> Hi,
>
> In running iozone for writes to small files, we noticed a pretty big
> discrepency between the performance of the deadline and cfq I/O
> schedulers. Investigation showed that I/O was being issued from 2
> different contexts: the iozone process itself, and the jbd2/sdh-8 thread
> (as expected). Because of the way cfq performs slice idling, the delays
> introduced between the metadata and data I/Os were significant. For
> example, cfq would see about 7MB/s versus deadline's 35 for the same
> workload. I also tested fs_mark with writing and fsyncing 1000 64k
> files, and a similar 5x performance difference was observed. Eric
> Sandeen suggested that I flag the journal writes as metadata, and once I
> did that, the performance difference went away completely (cfq has
> special logic to prioritize metadata I/O).
>
> 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.
Looks good to me.
--
Jens Axboe
next prev parent reply other threads:[~2010-04-02 7:00 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 [this message]
2010-04-05 17:52 ` tytso
2010-04-05 18:36 ` Jeff Moyer
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=20100402070001.GY23510@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=esandeen@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).