From: Kay Sievers <kay.sievers@vrfy.org>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
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 12:16:42 +0100 [thread overview]
Message-ID: <ac3eb2510902200316m387ecb45n86a2ea7c6196b01@mail.gmail.com> (raw)
In-Reply-To: <20090220094356.GB26124@silver.sucs.org>
On Fri, Feb 20, 2009 at 10:43, Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
> 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'"
Udev can write to the attribute itself. This should be all you need:
SUSBSYTEM=="block", ATTRS{model}=="ASUS-PHISON *", ATTR{queue/rotational}="1"
Kay
next prev parent reply other threads:[~2009-02-20 11:16 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
2009-02-20 10:37 ` Justin Piszcz
2009-02-20 10:44 ` Sitsofe Wheeler
2009-02-20 11:16 ` Kay Sievers [this message]
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=ac3eb2510902200316m387ecb45n86a2ea7c6196b01@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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®