Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
| From: | Andrew Morton <akpm-AT-linux-foundation.org> | |
| To: | Eric Sandeen <sandeen-AT-redhat.com> | |
| Subject: | Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes | |
| Date: | Fri, 16 May 2008 13:05:45 -0700 | |
| Message-ID: | <20080516130545.845a3be9.akpm@linux-foundation.org> | |
| Cc: | linux-ext4-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org, linux-fsdevel-AT-vger.kernel.org, jamie-AT-shareable.org | |
| Archive‑link: | Article |
On Fri, 16 May 2008 14:02:46 -0500 Eric Sandeen <sandeen@redhat.com> wrote: > A collection of patches to make ext3 & 4 use barriers by > default, and to call blkdev_issue_flush on fsync if they > are enabled. Last time this came up lots of workloads slowed down by 30% so I dropped the patches in horror. I just don't think we can quietly go and slow everyone's machines down by this much. The overhead of journalling is already pretty horrid. If we were seeing a significant number of "hey, my disk got wrecked" reports which attributable to this then yes, perhaps we should change the default. But I've never seen _any_, although I've seen claims that others have seen reports. There are no happy solutions here, and I'm inclined to let this dog remain asleep and continue to leave it up to distributors to decide what their default should be. Do we know which distros are enabling barriers by default? -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
(Log in to post comments)