All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Klaver <fransklaver@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel <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:27:46 +0200	[thread overview]
Message-ID: <CAH6sp9P+9hkanT0et-5L=fQ1QTJxwf6wof9589dEb_sRRpLDmw@mail.gmail.com> (raw)
In-Reply-To: <CAAJw_ZuazTK1b_W2Ys4BQZUQb=tGsMguc1PXsByeHgL2ATaPJQ@mail.gmail.com>

On Tue, Jun 23, 2015 at 5:02 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Mon, Jun 22, 2015 at 11:36 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> On Mon, Jun 22, 2015 at 03:25:29PM +0800, Jeff Chua wrote:
>>>
>>> There's no need to wait for disk spin-up for USB SSD devices. This patch
>>> allow the SSD to skip waiting disk spin-up by passing sd_mod.ssd=1 during
>>> boot-up.
>>>
>>> If there's a better way to handle this, please share.
>>
>> Module parameters are never a solution for a device-specific property,
>> sorry.
>
> Greg,
>
> SSD is coming mainstream and it doesn't make sense wasting time
> spinning up "disk" ...

I don't think Greg disputes that. He just objects to the solution (a
module parameter) you proposed. I'd guess that detecting that we're
talking to an SSD and then skipping the wait would make more sense, if
at all possible.

Frans

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  7:25 Stop SSD from waiting for "Spinning up disk..." Jeff Chua
2015-06-22 15:36 ` Greg Kroah-Hartman
2015-06-23 15:02   ` Jeff Chua
2015-06-23 18:27     ` Frans Klaver [this message]
2015-06-23 18:51     ` Marc Burkhardt
2015-06-25 16:21 ` Henrique de Moraes Holschuh
2015-06-25 16:47   ` Joe Perches
2015-06-23 18:26 Andreas Mohr
2015-06-23 18:55 ` Martin Steigerwald
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

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='CAH6sp9P+9hkanT0et-5L=fQ1QTJxwf6wof9589dEb_sRRpLDmw@mail.gmail.com' \
    --to=fransklaver@gmail.com \
    --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 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.