All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Jan Ceuleers <jan.ceuleers@computer.org>,
	"Peter M. Petrakis" <peter.petrakis@canonical.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>
Subject: Re: Is there a reliable way to ID a SSD?
Date: Thu, 06 Jan 2011 13:55:30 -0500	[thread overview]
Message-ID: <4D261022.3030902@garzik.org> (raw)
In-Reply-To: <AANLkTim=AxrJybApL-5oG7+i08tkKofk0eyP+3XhjhBJ@mail.gmail.com>

On 01/06/2011 01:40 PM, Greg Freemyer wrote:
> (resend, sorry for the duplicate)
>
> Jeff,
>
> As the maintainer, can you provide direction as to how quirks should
> be maintained for the rotating disk flag (as reflected in
> /sys/block/sda/queue/rotational).
>
> There is Bart's patch, Peter's patch, and Martin says it can be
> overridden from userspace (I'm not sure which tool,  nor do I know if
> there is already a userspace quirks table to add to.).
>
> Bart's atang PATCH: http://marc.info/?l=linux-ide&m=126677421807814&w=2
>
> Peter's patch: http://www.spinics.net/lists/linux-ide/msg38944.html

There are a long list of non-rotational devices that were produced 
before the ATA standard grew a standard method of reporting that device 
attribute.

That implies any approach individually listing products will create a 
very, very long horkage list containing all ATA flash drives that anyone 
ever produced.

Alternately, scanning for the "SSD" string does not seem very useful, 
because it will only match a tiny minority of first-run products that 
(a) call themselves "SSD" in marketing literature but (b) do not 
indicate proper rotational attributes in the IDENTIFY page.  Because 
while non-rotational products have been around for a very long time, 
"SSDs" as they are a currently known are new.

It seems like a project to retroactively identify ATA non-rotational 
products will be long and on-going, and would be better suited to a 
userspace package such as Tejun's storage-fixup: 
http://git.kernel.org/?p=linux/kernel/git/tj/storage-fixup.git

	Jeff




  reply	other threads:[~2011-01-06 18:55 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
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 [this message]
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=4D261022.3030902@garzik.org \
    --to=jeff@garzik.org \
    --cc=greg.freemyer@gmail.com \
    --cc=jan.ceuleers@computer.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=peter.petrakis@canonical.com \
    --cc=tj@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.