All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Mark Lord <liml@rtr.ca>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patch] libata resume fix
Date: Tue, 30 May 2006 14:40:15 -0400	[thread overview]
Message-ID: <447C918F.2080801@emc.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605301122340.5623@g5.osdl.org>

Linus Torvalds wrote:

>On Tue, 30 May 2006, Mark Lord wrote:
>  
>
>>Not in a suspend/resume capable notebook, though.
>>
>>I don't know of *any* notebook drives that take longer
>>than perhaps five seconds to spin-up and accept commands.
>>Such a slow drive wouldn't really be tolerated by end-users,
>>which is why they don't exist.
>>    
>>
>
>Indeed. In fact, I'd be surprised to see it in a desktop too.
>
>At least at one point, in order to get a M$ hw qualification (whatever 
>it's called - but every single hw manufacturer wants it, because some 
>vendors won't use your hardware if you don't have it), a laptop needed to 
>boot up in less than 30 seconds or something.
>
>And that wasn't the disk spin-up time. That was the time until the Windows 
>desktop was visible.
>
>Desktops could do a bit longer, and I think servers didn't have any time 
>limits, but the point is that selling a disk that takes a long time to 
>start working is actually not that easy. 
>
>The market that has accepted slow bootup times is historically the server 
>market (don't ask me why - you'd think that with five-nines uptime 
>guarantees you'd want fast bootup), and so you'll find large SCSI disks in 
>particular with long spin-up times. In the laptop and desktop space I'd be 
>very surprised to see anythign longer than a few seconds.
>
>		Linus
>  
>
With many data centera applications, delayed spin up of SCSI (and 
increasingly S-ATA) drives is a feature meant to avoid blowing a circuit 
when you spin up too many drives at once ;-)

Ric


  reply	other threads:[~2006-05-30 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 20:34 [git patch] libata resume fix Jeff Garzik
2006-05-29 21:34 ` Benjamin Herrenschmidt
2006-05-30 13:22   ` Mark Lord
2006-05-30 18:26     ` Linus Torvalds
2006-05-30 18:40       ` Ric Wheeler [this message]
2006-05-30 22:37       ` Benjamin Herrenschmidt
2006-05-31  6:47         ` Jens Axboe
2006-05-31  6:56           ` Benjamin Herrenschmidt
2006-05-31 22:01       ` Bill Davidsen
2006-05-30 22:34     ` Benjamin Herrenschmidt
     [not found] <6hAdo-5CV-5@gated-at.bofh.it>
     [not found] ` <6hXD0-6Y9-1@gated-at.bofh.it>
     [not found]   ` <6icsx-4vp-33@gated-at.bofh.it>
     [not found]     ` <6ih8Y-3ba-15@gated-at.bofh.it>
     [not found]       ` <6iH3h-2xw-59@gated-at.bofh.it>
2006-06-01  3:27         ` Robert Hancock
2006-06-01 13:48           ` Jens Axboe
2006-06-01 14:20             ` Bill Davidsen
2006-06-06  6:54             ` Tejun Heo
2006-06-06  7:05               ` Jens Axboe
2006-06-06  7:10                 ` Tejun Heo

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=447C918F.2080801@emc.com \
    --to=ric@emc.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.