mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 14:23:38 +0100	[thread overview]
Message-ID: <ac3eb2510902200523o619e64aas7bffac9aeca86814@mail.gmail.com> (raw)
In-Reply-To: <20090220131209.GA21446@silver.sucs.org>

On Fri, Feb 20, 2009 at 14:12, Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
> On Fri, Feb 20, 2009 at 12:16:42PM +0100, Kay Sievers wrote:
>>
>> Udev can write to the attribute itself. This should be all you need:
>>   SUSBSYTEM=="block", ATTRS{model}=="ASUS-PHISON *", ATTR{queue/rotational}="1"
>
> I tried
> SUBSYSTEM=="block", ATTRS{model}=="ASUS-PHISON *", ATTR{queue/rotational}="0"
> but udevtest /sys/block/sda/ doesn't list it as firing (udev 117-8)...

I does here:
  udev_rules_apply_to_event: ATTR '/sys/devices/ ...
/sdb/queue/rotational' writing '0'

  $grep . /sys/class/block/*/queue/rotational
  /sys/class/block/sda/queue/rotational:1
  /sys/class/block/sdb/queue/rotational:0

Maybe "udevtest" is not showing it for you, or udev 117 is too old and
does not work that way.

Thanks,
Kay

  reply	other threads:[~2009-02-20 13:23 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
2009-02-20 13:12     ` Sitsofe Wheeler
2009-02-20 13:23       ` Kay Sievers [this message]
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=ac3eb2510902200523o619e64aas7bffac9aeca86814@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®