From: Alex Shi <alex.shi@linaro.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>,
Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
Linaro Kernel <linaro-kernel@lists.linaro.org>
Cc: stable@vger.kernel.org
Subject: Re: a old issue of ext4 on lts 3.10
Date: Sun, 17 May 2015 23:19:52 +0800 [thread overview]
Message-ID: <5558B198.4040609@linaro.org> (raw)
In-Reply-To: <87bnhmrj5c.fsf@openvz.org>
On 05/15/2015 04:36 AM, Dmitry Monakhov wrote:
> Alex Shi <alex.shi@linaro.org> writes:
>
>> > Hi Dmitry&Theodore,
>> >
>> > Someone said without the following patch on lts 3.10 kernel (which used
>> > as android base kernel). the write maybe very very slow, needs 1 or 2
>> > seconds to finish.
> In fact this was an optimization.
> wait_for_stable_page() is actually and optimized wait_on_page_writeback()
Hi, Dimtry, it *is* a optimization, the fault is just happened *without*
this patch, not with this. :)
The curious for me is why this patch has this effect. It looks like the
new func just wait page wb when the device support data integrity. But
Why the data integrity device need to wait wb, while other device don't
need?
BTW,
how to know if my disk support data integrity. My harddisk spec said it
has this feature, but my linux kernel with integrity supported don't
have /sys/block/sdx/integrity.
Thanks a lots for your quick response!
>
> see:
> void wait_for_stable_page(struct page *page)
> {
> struct address_space *mapping = page_mapping(page);
> struct backing_dev_info *bdi =
> mapping->backing_dev_info;
>
> if (!bdi_cap_stable_pages_required(bdi))
> return;
>
> wait_on_page_writeback(page);
> }
> It is very unlikely the patch provokes such huge slowdown.
> Can you please repeat your measurements and double check your evidence.
next prev parent reply other threads:[~2015-05-17 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 14:40 a old issue of ext4 on lts 3.10 Alex Shi
2015-05-14 20:36 ` Dmitry Monakhov
2015-05-17 15:19 ` Alex Shi [this message]
2015-05-18 6:41 ` Jan Kara
2015-05-20 3:04 ` Alex Shi
2015-05-18 6:21 ` Jan Kara
2015-05-20 2:58 ` Alex Shi
2015-05-21 9:28 ` Alex Shi
2015-05-21 16:51 ` gregkh
2015-05-22 8:26 ` Jan Kara
2015-05-24 2:54 ` Alex Shi
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=5558B198.4040609@linaro.org \
--to=alex.shi@linaro.org \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@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).