From: Ted Ts'o <tytso@mit.edu>
To: Tao Ma <tm@tao.ma>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] jbd2: Use WRITE_SYNC in journal checkpoint.
Date: Mon, 27 Jun 2011 12:41:58 -0400 [thread overview]
Message-ID: <20110627164158.GD2729@thunk.org> (raw)
In-Reply-To: <1307418559-3329-1-git-send-email-tm@tao.ma>
On Tue, Jun 07, 2011 at 11:49:19AM +0800, Tao Ma wrote:
> From: Tao Ma <boyu.mt@taobao.com>
>
> In journal checkpoint, we write the buffer and wait for its finish.
> But in cfq, the async queue has a very low priority, and in our test,
> if there are too many sync queues and every queue is filled up with
> requests, the write request will be delayed for quite a long time and
> all the tasks which are waiting for journal space will end with errors like:
Thanks, added to the ext4 patch tree.
- Ted
prev parent reply other threads:[~2011-06-27 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 3:49 [PATCH] jbd2: Use WRITE_SYNC in journal checkpoint Tao Ma
2011-06-14 15:22 ` Tao Ma
2011-06-27 16:41 ` Ted Ts'o [this message]
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=20110627164158.GD2729@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
/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).