From: Jan Kara <jack@suse.cz>
To: "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@cn.bosch.com>
Cc: Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"Li, Michael" <huayil@qti.qualcomm.com>
Subject: Re: ext4 out of order when use cfq scheduler
Date: Thu, 24 Mar 2016 13:17:32 +0100 [thread overview]
Message-ID: <20160324121732.GE4025@quack.suse.cz> (raw)
In-Reply-To: <ac387f41e9604a229d680a94930b74d9@SGPMBX1004.APAC.bosch.com>
On Thu 24-03-16 10:16:05, HUANG Weller (CM/ESW12-CN) wrote:
> >
> > OK, I have something - Huang, can you check whether the attached patches also
> > fix your data exposure issues please? The first patch is the original fix, patch two
> > is a cleanup, patches 3 and 4 implement the speedup suggested by Ted. Patches
> > are only lightly tested so far. I'll run more comprehensive tests later and in
> > particular I want to check whether the additional complexity actually brings us
> > some advantage at least for workloads which redirty pages in addition to writing
> > some new ones using delayed allocation.
> >
>
> Test done.
> Both targets(kernel 3.10.63) PASS the power loss test with 10,000 cycles. Test with io-scheduler CFQ.
Thanks for testing! I'll submit those patches once I verify there is some
performance gain in only waiting...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-03-24 12:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 6:24 ext4 out of order when use cfq scheduler HUANG Weller (CM/EPF1-CN)
2015-12-22 15:00 ` Jan Kara
[not found] ` <c67f356b63d94d35ad010a6e987b68f0@SGPMBX1004.APAC.bosch.com>
2016-01-05 15:30 ` Jan Kara
2016-01-06 2:39 ` HUANG Weller (CM/ESW12-CN)
2016-01-06 19:17 ` Andreas Dilger
2016-01-07 6:51 ` HUANG Weller (CM/ESW12-CN)
[not found] ` <20160106100621.GA24046@quack.suse.cz>
[not found] ` <3ab48fa47e434455b101251730e69bd2@SGPMBX1004.APAC.bosch.com>
2016-01-07 10:24 ` Jan Kara
2016-01-07 11:02 ` HUANG Weller (CM/ESW12-CN)
2016-01-07 11:47 ` Jan Kara
2016-01-07 12:19 ` Jan Kara
2016-01-08 2:18 ` HUANG Weller (CM/ESW12-CN)
2016-01-08 0:46 ` HUANG Weller (CM/ESW12-CN)
2016-01-11 9:05 ` HUANG Weller (CM/ESW12-CN)
2016-01-11 10:21 ` Jan Kara
2016-03-13 4:27 ` Theodore Ts'o
2016-03-14 2:43 ` HUANG Weller (CM/ESW12-CN)
2016-03-14 7:39 ` Jan Kara
2016-03-14 14:36 ` Theodore Ts'o
2016-03-15 10:46 ` Jan Kara
2016-03-15 14:46 ` Jan Kara
2016-03-15 20:09 ` Jan Kara
2016-03-16 2:30 ` HUANG Weller (CM/ESW12-CN)
2016-03-18 9:20 ` Jan Kara
2016-06-22 11:55 ` FW: " HUANG Weller (CM/ESW12-CN)
2016-06-22 13:09 ` Jan Kara
2016-03-16 0:41 ` HUANG Weller (CM/ESW12-CN)
2016-03-24 10:16 ` HUANG Weller (CM/ESW12-CN)
2016-03-24 12:17 ` Jan Kara [this message]
2016-01-28 8:02 ` Xiong Zhou
2016-02-03 6:08 ` HUANG Weller (CM/ESW12-CN)
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=20160324121732.GE4025@quack.suse.cz \
--to=jack@suse.cz \
--cc=Weller.Huang@cn.bosch.com \
--cc=huayil@qti.qualcomm.com \
--cc=linux-ext4@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).