public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: Stop SSD from waiting for "Spinning up disk..."
Date: Tue, 23 Jun 2015 20:55:49 +0200	[thread overview]
Message-ID: <3819569.ix7n6b03GW@merkaba> (raw)
In-Reply-To: <20150623182612.GA27461@rhlx01.hs-esslingen.de>

Am Dienstag, 23. Juni 2015, 20:26:12 schriebst Du:
> Hi,

Hi,

> [proper In-Reply-To trail missing since lkml.org now fails to provide it]
[…]
> > Greg,
> > 
> > SSD is coming mainstream and it doesn't make sense wasting time
> > spinning up "disk" ...
> 
> ...which probably is not truly being achieved
> by providing a *custom* kernel parameter
> which does apply to only those disk instances
> which some users *specifically* care about.
> 
> Some things come to mind:
> 
> - at this scope, generally spoken
>   one shouldn't be concerned with whether "we are SSD",
>   but rather whether "we (do not) need spinup"
>   (which might apply to a ton of different SCSI-based storage devices,
>   even some SAN-based platter-based ones)
>   *This* is what this is about
>   (and this could then have been reflected in kernel parameter naming)
[…]
> - the kernel must already have some mechanisms to discern between
> (non-)platters (e.g. perhaps for knowing whether to support SSD TRIM
> command)

Yep, for the first SSD in this laptop:

merkaba:/sys> cat 
./devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/queue/rotational
0

[…]

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2015-06-23 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 18:26 Stop SSD from waiting for "Spinning up disk..." Andreas Mohr
2015-06-23 18:55 ` Martin Steigerwald [this message]
2015-06-24 16:22   ` Jeff Chua
2015-06-24 16:28     ` Greg Kroah-Hartman
2015-06-24 23:55       ` Jeff Chua
2015-06-25  1:41         ` Greg Kroah-Hartman
2015-06-25  6:08           ` Martin Steigerwald
2015-06-25  8:52             ` Jeff Chua
  -- strict thread matches above, loose matches on Subject: below --
2015-06-22  7:25 Jeff Chua
2015-06-22 15:36 ` Greg Kroah-Hartman
2015-06-23 15:02   ` Jeff Chua
2015-06-23 18:27     ` Frans Klaver
2015-06-23 18:51     ` Marc Burkhardt
2015-06-25 16:21 ` Henrique de Moraes Holschuh
2015-06-25 16:47   ` Joe Perches

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=3819569.ix7n6b03GW@merkaba \
    --to=martin@lichtvoll.de \
    --cc=andi@lisas.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@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