From: Kerin Millar <kerframil@gmail.com>
To: xfs@oss.sgi.com
Subject: Backporting the concurrent direct IO write fix to 3.4
Date: Tue, 03 Jul 2012 14:31:11 +0100 [thread overview]
Message-ID: <4FF2F41F.5000504@gmail.com> (raw)
Hi,
I recently became aware of commit 507630b2 (use shared ilock mode for
direct IO writes by default). I understand that this fixes a regression
which can have a notable impact upon MySQL performance. This is of
considerable interest to myself because my MySQL servers have to contend
with a really tough workload.
The patch applies cleanly to 3.4 stable but is it actually safe to use
it there? Or does it depend on other changes to XFS, such that I'd be
better off holding out for 3.5? Any advice would be greatly appreciated.
Cheers,
--Kerin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-07-03 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 13:31 Kerin Millar [this message]
2012-07-03 16:09 ` Backporting the concurrent direct IO write fix to 3.4 Christoph Hellwig
2012-07-03 23:11 ` Dave Chinner
2012-07-04 4:09 ` Igor M Podlesny
2012-07-04 8:02 ` Dave Chinner
2012-07-04 5:54 ` Christoph Hellwig
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=4FF2F41F.5000504@gmail.com \
--to=kerframil@gmail.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