From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 71641] Unreasonable performance degradation in ext4 with full data journaling
Date: Thu, 20 Mar 2014 04:09:50 +0000 [thread overview]
Message-ID: <bug-71641-13602-XwG9byeCbK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71641-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71641
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #4 from Theodore Tso <tytso@mit.edu> ---
Could you retry your measurements using the latest kernel? At least 3.11, and
preferably 3.13.
We significantly optimized the write path for the nodelalloc case in 3.11.
That should fix the average size being so small for the nodelalloc case:
commit 20970ba65d5a22f2e4efbfa100377722fde56935
Author: Theodore Ts'o <tytso@mit.edu>
Date: Thu Jun 6 14:00:46 2013 -0400
ext4: use ext4_da_writepages() for all modes
Rename ext4_da_writepages() to ext4_writepages() and use it for all
modes. We still need to iterate over all the pages in the case of
data=journalling, but in the case of nodelalloc/data=ordered (which is
what file systems mounted using ext3 backwards compatibility will use)
this will allow us to use a much more efficient I/O submission path.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-20 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 11:39 [Bug 71641] New: Unreasonable performance degradation in ext4 with full data journaling bugzilla-daemon
2014-03-07 16:20 ` Theodore Ts'o
2014-03-07 16:20 ` [Bug 71641] " bugzilla-daemon
2014-03-07 17:57 ` bugzilla-daemon
2014-03-19 9:35 ` bugzilla-daemon
2014-03-20 4:09 ` bugzilla-daemon [this message]
2014-03-20 12:47 ` bugzilla-daemon
2014-03-21 8:16 ` bugzilla-daemon
2014-03-21 8:17 ` bugzilla-daemon
2014-03-21 8:44 ` bugzilla-daemon
2014-03-21 8:48 ` bugzilla-daemon
2014-03-21 16:04 ` bugzilla-daemon
2014-03-26 10:30 ` bugzilla-daemon
2014-03-26 13:40 ` bugzilla-daemon
2014-03-28 10:23 ` bugzilla-daemon
2014-03-28 10:55 ` bugzilla-daemon
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=bug-71641-13602-XwG9byeCbK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).