From: CAI Qian <caiqian@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: possible fsync02() xfs slowness regression on power7
Date: Sun, 3 Mar 2013 23:23:26 -0500 (EST) [thread overview]
Message-ID: <1601552351.8516567.1362371006444.JavaMail.root@redhat.com> (raw)
In-Reply-To: <220575861.7590457.1362129618880.JavaMail.root@redhat.com>
> > And this commit in 3.9-rc1:
> >
> > a1e16c2 xfs: limit speculative prealloc size on sparse files
> > should fix the problem. Please confirm these commits are the cause
> > and the fix respectively....
Confirmed this fixed the problem. I'd like to request this to be back-ported
to stable-3.0, stable-3.4 and stable-3.8. What do you think?
Thanks,
CAI Qian
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-04 4:23 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 ` possible fsync02() xfs slowness regression on power7 CAI Qian
2013-02-28 11:54 ` Dave Chinner
2013-03-01 9:20 ` CAI Qian
2013-03-04 4:23 ` CAI Qian [this message]
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=1601552351.8516567.1362371006444.JavaMail.root@redhat.com \
--to=caiqian@redhat.com \
--cc=david@fromorbit.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