From: Paul Taysom <taysom@chromium.org>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jack@suse.cz, taysom@chromium.org, sonnyrao@chromium.org
Subject: [PATCH] fs: sync: fixed performance regression
Date: Wed, 10 Jul 2013 16:12:36 -0700 [thread overview]
Message-ID: <1373497956-8770-1-git-send-email-taysom@chromium.org> (raw)
The following commit introduced a 10x regression for
syncing inodes in ext4 with relatime enabled where just
the atime had been modified.
commit 4ea425b63a3dfeb7707fc7cc7161c11a51e871ed
Author: Jan Kara <jack@suse.cz>
Date: Tue Jul 3 16:45:34 2012 +0200
vfs: Avoid unnecessary WB_SYNC_NONE writeback during sys_sync and reorder sync passes
See also: http://www.kernelhub.org/?msg=93100&p=2
Fixed by putting back in the call to writeback_inodes_sb.
I'll attach the test in a reply to this e-mail.
The test starts by creating 512 files, syncing, reading one byte
from each of those files, syncing, and then deleting each file
and syncing. The time to do each sync is printed. The process
is then repeated for 1024 files and then the next power of
two up to 262144 files.
Note, when running the test, the slow down doesn't always happen
but most of the tests will show a slow down.
In response to crbug.com/240422
Signed-off-by: Paul Taysom <taysom@chromium.org>
---
fs/sync.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/fs/sync.c b/fs/sync.c
index 905f3f6..55c3316 100644
--- a/fs/sync.c
+++ b/fs/sync.c
@@ -73,6 +73,12 @@ static void sync_inodes_one_sb(struct super_block *sb, void *arg)
sync_inodes_sb(sb);
}
+static void writeback_inodes_one_sb(struct super_block *sb, void *arg)
+{
+ if (!(sb->s_flags & MS_RDONLY))
+ writeback_inodes_sb(sb, WB_REASON_SYNC);
+}
+
static void sync_fs_one_sb(struct super_block *sb, void *arg)
{
if (!(sb->s_flags & MS_RDONLY) && sb->s_op->sync_fs)
@@ -104,6 +110,7 @@ SYSCALL_DEFINE0(sync)
int nowait = 0, wait = 1;
wakeup_flusher_threads(0, WB_REASON_SYNC);
+ iterate_supers(writeback_inodes_one_sb, NULL);
iterate_supers(sync_inodes_one_sb, NULL);
iterate_supers(sync_fs_one_sb, &nowait);
iterate_supers(sync_fs_one_sb, &wait);
--
1.8.3
next reply other threads:[~2013-07-10 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 23:12 Paul Taysom [this message]
2013-07-10 23:45 ` [PATCH] fs: sync: fixed performance regression Paul Taysom
2013-07-10 23:56 ` Dave Jones
2013-07-11 0:42 ` Paul Taysom
2013-07-11 0:45 ` Paul Taysom
2013-07-11 2:00 ` Dave Chinner
2013-07-11 10:53 ` Jan Kara
2013-07-11 11:58 ` Jan Kara
2013-07-11 21:42 ` Paul Taysom
2013-07-12 15:43 ` Jan Kara
2013-07-12 16:59 ` Paul Taysom
2013-07-15 9:46 ` Jan Kara
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=1373497956-8770-1-git-send-email-taysom@chromium.org \
--to=taysom@chromium.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonnyrao@chromium.org \
--cc=viro@zeniv.linux.org.uk \
/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).