All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Joe Ceklosky <jfceklosky@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: SSD slowdown with 3.3.X?
Date: Fri, 20 Apr 2012 11:23:25 -0400	[thread overview]
Message-ID: <x49ehriwhoy.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4F8F82EC.1060708@teksavvy.com> (Mark Lord's message of "Wed, 18 Apr 2012 23:13:48 -0400")

Mark Lord <kernel@teksavvy.com> writes:

> On 12-04-18 10:15 PM, Joe Ceklosky wrote:
>> All,
>> 
>> Has anyone reported slowness using SSD's on kernel 3.3.X compiled
>> as 32-bit PAE with 16 Gigs of memory (I know I need to update to 64-bit
>> already, will do with Fedora 17)?
>> 
>> I am see terrible r/w to an SSD using 3.3.2.  When I boot the same machine
>> and SSD back in 3.2.15 all is fine.
>
>
> Double check which IO-scheduler the kernel is choosing.
> For SSDs, it is normally "noop", but I noticed "cfq"
> being chosen instead for some reason.

The default I/O scheduler is the default I/O scheduler.  Drivers may
override this (some high-end PCIe SSD drivers do this, and I think s390
block drivers do as well), but in general the default is left alone.

Cheers,
Jeff

  reply	other threads:[~2012-04-20 15:23 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 [this message]
     [not found]   ` <4F90C4CF.1010000@gmail.com>
2012-04-21  2:40     ` Mark Lord
2012-04-21  2:43       ` Mark Lord
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=x49ehriwhoy.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=jfceklosky@gmail.com \
    --cc=kernel@teksavvy.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.