From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: ffsb create_4k 16% regression
Date: Wed, 01 Jul 2009 13:33:00 +0800 [thread overview]
Message-ID: <1246426380.2560.473.camel@ymzhang> (raw)
In-Reply-To: <1246262818.2560.443.camel@ymzhang>
On Mon, 2009-06-29 at 16:06 +0800, Zhang, Yanmin wrote:
> I run many ffsb test cases on JBODs (typically 13/12 disks). Comparing
> with kernel 2.6.30, 2.6.31-rc1 has about 16% regression with
> ffsb_create_4k. The sub test case creates files continuously for 10
> minitues and every file is 1MB.
>
> Bisect located below patch.
>
>
> 5cee5815d1564bbbd505fea86f4550f1efdb5cd0 is first bad commit
> commit 5cee5815d1564bbbd505fea86f4550f1efdb5cd0
> Author: Jan Kara <jack@suse.cz>
> Date: Mon Apr 27 16:43:51 2009 +0200
>
> vfs: Make sys_sync() use fsync_super() (version 4)
>
> It is unnecessarily fragile to have two places (fsync_super() and do_sync())
> doing data integrity sync of the filesystem. Alter __fsync_super() to
> accommodate needs of both callers and use it. So after this patch
> __fsync_super() is the only place where we gather all the calls needed to
> properly send all data on a filesystem to disk.
>
>
> As a matter of fact, ffsb calls sys_sync in the end to make sure all data is
> flushed to disks and the flushing is counted into the result. vmstat shows
> ffsb is blocked when syncing for a long time. With 2.6.30, ffsb is blocked for
> a short time.
>
> I checked the patch and did experiments to recover the original methods. Eventually,
> the root cause is the patch deletes the calling to wakeup_pdflush when syncing, so
> only ffsb is blocked on disk I/O. wakeup_pdflush could ask pdflush to write back pages
> with ffsb at the same time.
>
> Below patch against 2.6.31-rc1 fixes it.
>
> Signed-off-by: Zhang Yanmin <yanmin_zhang@linux.intel.com>
>
> ---
>
> --- linux-2.6.31-rc1/fs/sync.c 2009-06-29 12:18:03.000000000 +0800
> +++ linux-2.6.31-rc1_sync/fs/sync.c 2009-06-29 14:56:49.000000000 +0800
> @@ -114,6 +114,7 @@ restart:
>
> SYSCALL_DEFINE0(sync)
> {
> + wakeup_pdflush(0);
> sync_filesystems(0);
> sync_filesystems(1);
> if (unlikely(laptop_mode))
Andrew,
Would you like to consider the patch for mm tree?
Thanks,
Yanmin
next prev parent reply other threads:[~2009-07-01 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 8:06 ffsb create_4k 16% regression Zhang, Yanmin
2009-07-01 5:33 ` Zhang, Yanmin [this message]
2009-07-01 5:46 ` Andrew Morton
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=1246426380.2560.473.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.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