[Top] [All Lists]

Backporting the concurrent direct IO write fix to 3.4

To: xfs@xxxxxxxxxxx
Subject: Backporting the concurrent direct IO write fix to 3.4
From: Kerin Millar <kerframil@xxxxxxxxx>
Date: Tue, 03 Jul 2012 14:31:11 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=3ZxjDJ/rQJFfCtLMN3IqbSLqq8t6LcbIyGIKT4Hy2C4=; b=nvOBkPzc0vavANHHOzyJomxQolIOpmkbP6wQp7qma6p8nJJU/fOUZ3SZzuBuJRHPgo mNe+u43PaETcU+rN8O5GAJx0MTjrTRT3KwHn2BMXwmhz6v/K0Y+DIIW5Y4W6/K4Rom8H LrQAgo6UdXhoLQdWctbPWGOnJsh6t7FXb7Ecwvy4lkSRvfFjLXQiN9TbngH617WTiUll 0i1ItpAObc7/IhzEz3Pknor7SnUTn3nEBif7HnRO3Q/XtVlCN03C9GdtnWqmKcPxUQuT LxwOYRNe5/YH8cdor017JSzdm8rVWd2/71KG+gIMxuknpLrlmOyFQfUzmORAqaNKVKo3 GL5Q==
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.5) Gecko/20120605 Thunderbird/10.0.5

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.



<Prev in Thread] Current Thread [Next in Thread>