From: Jonathan Corbet <corbet@lwn.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dramatic I/O slowdown after upgrading 2.6.32->3.0
Date: Mon, 2 Apr 2012 10:58:50 -0600 [thread overview]
Message-ID: <20120402105850.270fe7f2@lwn.net> (raw)
In-Reply-To: <4F75E46E.2000503@msgid.tls.msk.ru>
On Fri, 30 Mar 2012 20:50:54 +0400
Michael Tokarev <mjt@tls.msk.ru> wrote:
> I'm observing a dramatic slowdown of several hosts after upgrading
> from 2.6.32.y to 3.0.x i686 kernels (in both cases from kernel.org,
> on both cases the last version is relatively latest).
>
> On 2.6.32 everything is fast. On 3.0 the same operations which goes
> instantly takes ages to complete.
[...]
> What's the way to debug this issue?
There is a huge gap between those two kernels, so nobody is going to have
much luck guessing about what has changed. A good first step might be to
do a binary search among the intermediate kernel releases to figure out
which one slowed things down for you.
jon
next prev parent reply other threads:[~2012-04-02 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:50 dramatic I/O slowdown after upgrading 2.6.32->3.0 Michael Tokarev
2012-04-02 16:58 ` Jonathan Corbet [this message]
2012-04-05 23:29 ` Jan Kara
2012-04-06 4:45 ` Michael Tokarev
2012-04-10 2:26 ` Dave Chinner
2012-04-10 6:00 ` dramatic I/O slowdown after upgrading 2.6.38->3.0+ Michael Tokarev
2012-04-10 15:13 ` Jan Kara
2012-04-10 19:25 ` Suresh Jayaraman
2012-04-10 19:51 ` Jan Kara
2012-04-11 0:20 ` Henrique de Moraes Holschuh
2012-04-11 9:40 ` Michael Tokarev
2012-04-11 17:19 ` Mike Christie
2012-04-11 17:55 ` Michael Tokarev
2012-04-11 18:28 ` Jan Kara
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=20120402105850.270fe7f2@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).