From: CAI Qian <caiqian@redhat.com>
To: xfs@oss.sgi.com
Cc: Steve Best <sbest@redhat.com>
Subject: possible fsync02() xfs slowness regression on power7
Date: Thu, 28 Feb 2013 04:28:35 -0500 (EST) [thread overview]
Message-ID: <2103242337.7001373.1362043715738.JavaMail.root@redhat.com> (raw)
In-Reply-To: <130819766.6999797.1362043338279.JavaMail.root@redhat.com>
This LTP test starting to fail using the latest upstream kernel on one of the power7
systems here, http://tinyurl.com/bngwouj
# ./fsync02
fsync02 1 TFAIL : fsync took too long: 252.000000 seconds; max_block: 214
When it is working, the test is almost returned immediately. The bisecting so far
indicated that one or a few of the following could be culprits.
# git log --pretty=oneline 498f7f505dc79934c878c7667840c50c64f232fc..b199c8a4ba11879df87daad496ceee41fdc6aa82
b199c8a4ba11879df87daad496ceee41fdc6aa82 xfs: Pull EFI/EFD handling out from under the AIL lock
9c5f8414efd5eeed9f498d4170337a3eb126341f xfs: fix EFI transaction cancellation.
821eb21d97a8b686649c08b7284d0b9f34d0e138 xfs: connect up buffer reclaim priority hooks
430cbeb86fdcbbdabea7d4aa65307de8de425350 xfs: add a lru to the XFS buffer cache
ff57ab21995a8636cfc72efeebb09cc6034d756f xfs: convert xfsbud shrinker to a per-buftarg shrinker.
1a427ab0c1b205d1bda8da0b77ea9d295ac23c57 xfs: convert pag_ici_lock to a spin lock
1a3e8f3da09c7082d25b512a0ffe569391e4c09a xfs: convert inode cache lookups to use RCU locking
d95b7aaf9ab6738bef1ebcc52ab66563085e44ac xfs: rcu free inodes
6e857567dbbfe14dd6cc3f7414671b047b1ff5c7 xfs: don't truncate prealloc from frequently accessed inodes
055388a3188f56676c21e92962fc366ac8b5cb72 xfs: dynamic speculative EOF preallocation
622d81494fa32343a4b97b607619656c7a4a6d1a xfs: use KM_NOFS for allocations during attribute list operations
dcfcf20512cb517ac18b9433b676183fa1257911 xfs: provide a inode iolock lockdep class
489a150f6454e2cd93d9e0ee6d7c5a361844f62a xfs: factor duplicate code in xfs_alloc_ag_vextent_near into a helper
9f9baab38dacd11fe6095a1e59f3783a305f7020 xfs: clean up xfs_alloc_ag_vextent_exact
ecff71e677c6d469f525dcf31ada709d5858307c xfs: simplify xfs_map_at_offset
aeea1b1f81800e362a3aca86d769d02e137a8fa7 xfs: refactor xfs_vm_writepage
2fa24f92530edaf86c3b5f662464e0d2e3b3e517 xfs: remove the all_bh flag from xfs_convert_page
ed1e7b7e484dfb64168755613d499f32a97409bd xfs: remove xfs_probe_cluster
8ff2957d581582890693affc09920108a67cb05d xfs: simplify xfs_map_blocks
a206c817c864583c44e2f418db8e6c7a000fbc38 xfs: kill xfs_iomap
CAI Qian
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2013-02-28 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <130819766.6999797.1362043338279.JavaMail.root@redhat.com>
2013-02-28 9:28 ` CAI Qian [this message]
2013-02-28 11:54 ` possible fsync02() xfs slowness regression on power7 Dave Chinner
2013-03-01 9:20 ` CAI Qian
2013-03-04 4:23 ` CAI Qian
2013-03-04 5:55 ` Dave Chinner
2013-03-04 6:14 ` CAI Qian
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=2103242337.7001373.1362043715738.JavaMail.root@redhat.com \
--to=caiqian@redhat.com \
--cc=sbest@redhat.com \
--cc=xfs@oss.sgi.com \
/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