From: Robert Hancock <hancockrwd@gmail.com>
To: "Benjamin S." <sbenni@gmx.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: bad performance with SSD since kernel version 2.6.32
Date: Mon, 22 Feb 2010 08:41:10 -0600 [thread overview]
Message-ID: <51f3faa71002220641n75c52dw661b86a77e44a0a1@mail.gmail.com> (raw)
In-Reply-To: <20100222141802.2bcbf607@pluto-lenny.milky.way>
CCing Rafael, this should be added to the list of known regressions.
On Mon, Feb 22, 2010 at 7:18 AM, Benjamin S. <sbenni@gmx.de> wrote:
>
> On Sun, 21 Feb 2010 16:00:35 -0600
> Robert Hancock <hancockrwd@gmail.com> wrote:
>
>> Hmm.. Well, that's not it then.. I suspect a bisection is likely the
>> easiest route at this point..
>
> fb1e75389bd06fd5987e9cda1b4e0305c782f854 is the first bad commit
> commit fb1e75389bd06fd5987e9cda1b4e0305c782f854
> Author: Jens Axboe <jens.axboe@oracle.com>
> Date: Thu Jul 30 08:18:24 2009 +0200
>
> block: improve queue_should_plug() by looking at IO depths
>
> Instead of just checking whether this device uses block layer
> tagging, we can improve the detection by looking at the maximum
> queue depth it has reached. If that crosses 4, then deem it a
> queuing device.
>
> This is important on high IOPS devices, since plugging hurts
> the performance there (it can be as much as 10-15% of the sys
> time).
>
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
>
>
>
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=fb1e75389bd06fd5987e9cda1b4e0305c782f854
>
>
> Without that patch my SSD (Super Talent Ultradrive GX MLC 64GB)
> reaches about 200MB/s sequentiell read. After applying the patch it
> reaches only 70MB/s.
>
>
>
> Note: Added Jens to CC.
>
>
next prev parent reply other threads:[~2010-02-22 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 13:28 bad performance with SSD since kernel version 2.6.32 Benjamin S.
2010-02-20 18:35 ` Robert Hancock
2010-02-21 1:26 ` Benjamin S.
[not found] ` <51f3faa71002210922i542c37f0j9e0e4a84d0977f90@mail.gmail.com>
[not found] ` <20100221225544.5a9ded51@pluto-lenny.milky.way>
[not found] ` <51f3faa71002211400u2177660ei1c0dc3d9306b146e@mail.gmail.com>
2010-02-22 13:18 ` Benjamin S.
2010-02-22 14:41 ` Robert Hancock [this message]
2010-02-22 19:05 ` Jens Axboe
2010-02-22 20:25 ` Benjamin S.
2010-02-23 6:22 ` Jens Axboe
2010-02-22 21:49 ` Mark Lord
2010-02-22 23:22 ` Robert Hancock
2010-02-23 6:21 ` Jens Axboe
2010-02-24 15:09 ` Mark Lord
2010-02-24 15:34 ` Jens Axboe
2010-02-24 15:48 ` Mark Lord
2010-02-24 19:05 ` Jens Axboe
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=51f3faa71002220641n75c52dw661b86a77e44a0a1@mail.gmail.com \
--to=hancockrwd@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sbenni@gmx.de \
/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).