From: Christoph Hellwig <hch@infradead.org>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
Laurent CORBES <laurent.corbes@smartjog.com>,
linux-kernel@vger.kernel.org
Subject: Re: Re: Ext3 sequential read performance drop 2.6.29 -> 2.6.30,2.6.31,...
Date: Tue, 3 Nov 2009 05:06:45 -0500 [thread overview]
Message-ID: <20091103100645.GA13118@infradead.org> (raw)
In-Reply-To: <20091102135554.b10ece3e.akpm@linux-foundation.org>
On Mon, Nov 02, 2009 at 01:55:54PM -0800, Andrew Morton wrote:
> On Tue, 13 Oct 2009 12:09:55 +0200
> Laurent CORBES <laurent.corbes@smartjog.com> 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.
next prev parent reply other threads:[~2009-11-03 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091013120955.6bd5844b@smartjog.com>
2009-10-13 13:10 ` Ext3 sequential read performance drop 2.6.29 -> 2.6.30,2.6.31, Laurent CORBES
2009-11-02 21:55 ` Andrew Morton
2009-11-03 10:06 ` Christoph Hellwig [this message]
2009-11-03 10:42 ` NeilBrown
2009-11-03 10:55 ` [dm-devel] " Laurent CORBES
2009-11-04 7:16 ` Neil Brown
2009-11-03 16:50 ` Andrew Morton
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=20091103100645.GA13118@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=laurent.corbes@smartjog.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).