All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: "Peter M. Petrakis" <peter.petrakis@canonical.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Is there a reliable way to ID a SSD?
Date: Tue, 04 Jan 2011 10:47:59 -0500	[thread overview]
Message-ID: <4D23412F.2080802@teksavvy.com> (raw)
In-Reply-To: <AANLkTi=Kv8f3e8zhSkDohkgJqOv+XKQ_dPR=aFbpzm27@mail.gmail.com>

On 11-01-03 05:50 PM, Greg Freemyer wrote:
>
> Would it be better if hdparm looked at /sys/block/sda/queue/rotational
> instead of just using word 217 of the identify block?
>
> The current divergence is:
>
> 1) The kernel routine  ata_id_rotation_rate() (in ata.h) is only
> trusting  word 217 if its ATA7 or higher.
>
> http://lxr.linux.no/#linux+v2.6.36/include/linux/ata.h#L799
>
> 2) There have been a couple proposed kernel patches to libata-scsi.c
> to quirk in a HORKAGE flag to set the rotation_rate to 1 (meaning SSD)
> for some known devices.  I don't see those being ACKed yet, but if one
> ever gets in, hdparm will diverge from the kernels info since its
> going straight to the identify block for its info.

That's what hdparm is for.  It reads only from the identify block
for most of the -I output, so that we (kernel developers) can see
exactly what the drive itself is reporting.

This reporting is what makes it useful, rather than simply parroting
whatever is already reported (or not) in /sys/

Cheers

  reply	other threads:[~2011-01-04 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 15:58 Is there a reliable way to ID a SSD? Greg Freemyer
2011-01-03 19:30 ` Peter M. Petrakis
2011-01-03 21:24   ` Greg Freemyer
2011-01-03 22:03     ` Peter M. Petrakis
2011-01-03 22:50       ` Greg Freemyer
2011-01-04 15:47         ` Mark Lord [this message]
2011-01-04 16:22           ` Greg Freemyer
2011-01-05  0:05         ` Martin K. Petersen
2011-01-06 16:10       ` Jan Ceuleers
     [not found]         ` <AANLkTin1ZjPmbk1M=9-SGStU7zLUozwxX7Ddtu53xNE2@mail.gmail.com>
2011-01-06 18:40           ` Greg Freemyer
2011-01-06 18:55             ` Jeff Garzik
2011-01-06 19:31             ` Martin K. Petersen
2011-01-06 20:11               ` Greg Freemyer
2011-01-06 20:41               ` Jeff Garzik
2011-01-06 21:54                 ` Martin K. Petersen
2011-01-06 19:23         ` Martin K. Petersen
2011-01-06 20:49           ` Jan Ceuleers
2011-01-06 22:02             ` Martin K. Petersen

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=4D23412F.2080802@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=peter.petrakis@canonical.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 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.