From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: General question (scheduler) with SSDs?
Date: Fri, 20 Feb 2009 09:43:56 +0000 [thread overview]
Message-ID: <20090220094356.GB26124@silver.sucs.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0902190837270.19552@p34.internal.lan>
Whoops, I didn't mean to send that previous half formed mail :) Sorry.
On Thu, Feb 19, 2009 at 08:38:38AM -0500, Justin Piszcz wrote:
>
> I was curious if anyone had done any benchmarks and/or has conclusive
> information, what is the best Linux scheduler to use with SSDs?
>
> Noop?
> CFQ?
> AS?
> Deadline?
As mentioned in another mail there was a discussion on
http://lkml.org/lkml/2009/1/31/28 and long thread talking about the
introduction of the rotational flag here
http://lkml.org/lkml/2009/1/5/340 . Cheapo SSDs or even USB keys are not
auto detected as non-rotational devices by the kernel and after a bit of
poking about I've come up with the following udev rules for my
particular cases:
SUBSYSTEM=="block", TEST=="/sys$devpath/queue/rotational", ATTRS{model}=="ASUS-PHISON *", RUN+="/bin/sh -c 'echo 0 > /sys$devpath/queue/rotational'"
SUBSYSTEM=="block", TEST=="/sys$devpath/queue/rotational", ATTRS{idVendor}=="0951", ATTRS{idProduct}=="1606", RUN+="/bin/sh -c 'echo 0 > /sys$devpath/queue/rotational'"
SUBSYSTEM=="block", TEST=="/sys$devpath/queue/rotational", ATTRS{manufacturer}=="SanDisk", ATTRS{product}=="Cruzer Micro", RUN+="/bin/sh -c 'echo 0 > /sys$devpath/queue/rotational'"
Ever since the rotational option appeared I've been trying cfq but prior
to that I was using noop or deadline. However it doesn't look like
anyone has sat down and run the numbers to see what affect the
ioscheulder/rotational flag is having on cheapo SSDs - all the
suggestions are anecdotal. Could you run some benchmarks with these
different options and report back the results?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-02-20 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 13:38 Justin Piszcz
2009-02-19 13:50 ` Pádraig Brady
2009-02-20 9:31 ` Sitsofe Wheeler
2009-02-20 9:43 ` Sitsofe Wheeler [this message]
2009-02-20 10:37 ` Justin Piszcz
2009-02-20 10:44 ` Sitsofe Wheeler
2009-02-20 11:16 ` Kay Sievers
2009-02-20 13:12 ` Sitsofe Wheeler
2009-02-20 13:23 ` Kay Sievers
2009-02-20 14:27 ` Sitsofe Wheeler
2009-02-20 14:56 ` Kay Sievers
2009-02-20 19:25 ` Sitsofe Wheeler
2009-02-20 19:35 ` Kay Sievers
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=20090220094356.GB26124@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@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
all inboxes | Powered by JetHome®