From: Phil Turmel <philip@turmel.org>
To: Dallas Clement <dallas.a.clement@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID 5,6 sequential writing seems slower in newer kernels
Date: Wed, 2 Dec 2015 21:34:11 -0500 [thread overview]
Message-ID: <565FAA23.2060504@turmel.org> (raw)
In-Reply-To: <CAE9DZUSRZ=bsga0G1UvfL3Dj-4W0ihXgOF=Ppqv=5-vz2+kAoQ@mail.gmail.com>
On 12/02/2015 09:24 PM, Dallas Clement wrote:
> On Wed, Dec 2, 2015 at 8:18 PM, Phil Turmel <philip@turmel.org> wrote:
>> I suspect if you do a bisect on the kernel to pinpoint the change(s)
>> that is doing this, you'll find a patch that closes a device-specific or
>> filesystem sync bug or something that enables deep queues for a device.
>>
>> Modern software that needs file integrity guarantees make sparse use of
>> fdatasync and/or fsync and avoid sync entirely. You'll have a more
>> believable test if you use fsync_on_close=1 or end_fsync=1.
>>
>> Phil
>
> Hi Phil. Hmm that makes sense that something may have changed wrt to
> syncing. Basically what I am trying to do with my fio testing is
> avoid any asynchronous or caching behavior.
I hope that if you really need this you are doing exhaustive testing on
failure modes -- I would be worried that these speed changes imply flaws
in the older kernels.
next prev parent reply other threads:[~2015-12-03 2:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 23:02 RAID 5,6 sequential writing seems slower in newer kernels Dallas Clement
2015-12-02 1:07 ` keld
2015-12-02 14:18 ` Robert Kierski
2015-12-02 14:45 ` Phil Turmel
2015-12-02 15:28 ` Robert Kierski
2015-12-02 15:37 ` Phil Turmel
2015-12-02 15:44 ` Robert Kierski
2015-12-02 15:51 ` Phil Turmel
2015-12-02 19:50 ` Dallas Clement
2015-12-03 0:12 ` Dallas Clement
2015-12-03 2:18 ` Phil Turmel
2015-12-03 2:24 ` Dallas Clement
2015-12-03 2:33 ` Dallas Clement
2015-12-03 2:38 ` Phil Turmel
2015-12-03 2:51 ` Dallas Clement
2015-12-03 4:30 ` Phil Turmel
2015-12-03 4:49 ` Dallas Clement
2015-12-03 13:43 ` Robert Kierski
2015-12-03 14:37 ` Phil Turmel
2015-12-03 2:34 ` Phil Turmel [this message]
2015-12-03 14:19 ` Robert Kierski
2015-12-03 14:39 ` Dallas Clement
2015-12-03 15:04 ` Phil Turmel
2015-12-03 22:21 ` Weedy
2015-12-04 13:40 ` Robert Kierski
2015-12-04 16:08 ` Dallas Clement
2015-12-07 14:29 ` Robert Kierski
2015-12-08 19:38 ` Dallas Clement
2015-12-08 21:24 ` Robert Kierski
2015-12-04 18:51 ` Shaohua Li
2015-12-05 1:38 ` Dallas Clement
2015-12-07 14:18 ` Robert Kierski
2015-12-02 15:37 ` Robert Kierski
2015-12-02 5:22 ` Roman Mamedov
2015-12-02 14:15 ` Robert Kierski
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=565FAA23.2060504@turmel.org \
--to=philip@turmel.org \
--cc=dallas.a.clement@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.