Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752425AbZKCKmj (ORCPT ); Tue, 3 Nov 2009 05:42:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752275AbZKCKmf (ORCPT ); Tue, 3 Nov 2009 05:42:35 -0500 Received: from cantor2.suse.de ([195.135.220.15]:50770 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752225AbZKCKmd (ORCPT ); Tue, 3 Nov 2009 05:42:33 -0500 From: "NeilBrown" To: "device-mapper development" , akpm@linux-foundation.org Date: Tue, 3 Nov 2009 21:42:30 +1100 Message-ID: In-Reply-To: <20091103100645.GA13118@infradead.org> References: <20091013120955.6bd5844b@smartjog.com> <20091102135554.b10ece3e.akpm@linux-foundation.org> <20091103100645.GA13118@infradead.org> Subject: Re: [dm-devel] Re: Ext3 sequential read performance drop 2.6.29 -> 2.6.30,2.6.31,... Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org, "Laurent CORBES" , linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1454 Lines: 37 On Tue, November 3, 2009 9:06 pm, Christoph Hellwig wrote: > On Mon, Nov 02, 2009 at 01:55:54PM -0800, Andrew Morton wrote: >> On Tue, 13 Oct 2009 12:09:55 +0200 >> Laurent CORBES wrote: >> >> > Hi all, >> > >> > While benchmarking some systems I discover a big sequential read >> performance >> > drop using ext3 on ~ big files. The drop seems to be introduced in >> 2.6.30. I'm >> > testing with 2.6.28.6 -> 2.6.29.6 -> 2.6.30.4 -> 2.6.31.3. >> >> Seems that large performance regressions aren't of interest to this >> list :( > > No sure which list you mean, but dm-devel is for dm, not md. We're also > seeing similarly massive performance drops with md and ext3/xfs as > already reported on the list. Someone tracked it down to writeback > changes as usual, but there it got stuck. I'm still looking - running some basic tests on 4 filesystems over half a dozen recent kernels to see what has been happening. I have a suspicion that there a multiple problems. In particular, XFS has a strange degradation which was papered over by commit c8a4051c3731b. I'm beginning to wonder if it was caused by commit 17bc6c30cf6bf but I haven't actually tested that yet. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/