From: Mark Lord <kernel@teksavvy.com>
To: Joe Ceklosky <jfceklosky@gmail.com>
Cc: "linux-ide@vger.kernel.org >> IDE/ATA development list"
<linux-ide@vger.kernel.org>
Subject: Re: SSD slowdown with 3.3.X?
Date: Fri, 20 Apr 2012 22:43:27 -0400 [thread overview]
Message-ID: <4F921ECF.2080303@teksavvy.com> (raw)
In-Reply-To: <4F921E18.6000301@teksavvy.com>
On 12-04-20 10:40 PM, Mark Lord wrote:
> On 12-04-19 10:07 PM, Joe Ceklosky wrote:
>> Mark,
>>
>>
>> Thanks for the info, but nothing like that shows up:
>>
>>
>> [jceklosk@neptune tmp]$ cat c-3.2.15
>> noop deadline [cfq]
>> noop deadline [cfq]
>>
>>
>> [jceklosk@neptune tmp]$ cat c-3.3.2
>> noop deadline [cfq]
>> noop deadline [cfq]
>
>
> Well, the stuff you posted (above) shows that cfq is being used
> instead of noop. For SSDs, noop is the more natural choice,
> and used to be the default in the kernel for a while.
> I wonder when that changed?
Looking into the block layer now, I see that "cfq" at some point
became "SSD aware", which is probably when the default io scheduler
for SSDs changed back to cfq from noop.
Not 100% sure, but that's how it appears now.
I still have my systems set it to noop when an SSD is detected.
next prev parent reply other threads:[~2012-04-21 2:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 2:15 SSD slowdown with 3.3.X? Joe Ceklosky
2012-04-19 3:13 ` Mark Lord
2012-04-20 15:23 ` Jeff Moyer
[not found] ` <4F90C4CF.1010000@gmail.com>
2012-04-21 2:40 ` Mark Lord
2012-04-21 2:43 ` Mark Lord [this message]
2012-04-21 3:53 ` Stan Hoeppner
2012-04-21 11:45 ` cwillu
2012-04-21 18:30 ` Stan Hoeppner
2012-04-23 12:44 ` Mark Lord
2012-04-25 0:22 ` Stan Hoeppner
2012-04-23 14:11 ` Jeff Moyer
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=4F921ECF.2080303@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=jfceklosky@gmail.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.