From: Bill Davidsen <davidsen@tmr.com>
To: Jens Axboe <axboe@suse.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [git patch] libata resume fix
Date: Thu, 01 Jun 2006 10:20:46 -0400 [thread overview]
Message-ID: <447EF7BE.1020005@tmr.com> (raw)
In-Reply-To: <20060601134802.GK4400@suse.de>
Jens Axboe wrote:
>On Wed, May 31 2006, Robert Hancock wrote:
>
>
>>Bill Davidsen wrote:
>>
>>
>>>The trade-off is that if I have a 15k rpm SCSI drive, it would take a
>>>lot of design changes to make it spin up quickly, and improve a function
>>>which is usually done on a server once every MTBF when replacing the
>>>failed unit.
>>>
>>>I think the majority of very large or very fast drives are in systems
>>>which don't (deliberately) power cycles often, in rooms where heat is an
>>>issue. And to spin up quickly take a larger power supply... 30 sec is
>>>fine with most users.
>>>
>>>Couldn't find a spin-up time for the new Seagate 750GB drive, but the
>>>seek sure is fast!
>>>
>>>
>>I wouldn't guess that even a 15K drive would take nearly that long. For
>>boot time on servers it doesn't matter much though, disk spinup time is
>>
>>
>
>I do use a 15K rpm drive in my workstation (hello git!), and the spin up
>really isn't that bad. Less than 10 seconds for the actual spin up, I
>would say.
>
>
Sounds about right, but clearly longer than the 2 sec mentioned early in
this thread. I think a long delay is okay as long as it gets stopped
when the drive does come ready.
>
>
>>in the noise compared to the insane BIOS delays on most of them during
>>bootup. Like on some servers (ahem.. IBM) which have about a 15 second
>>delay on the main BIOS screen, 10 second delays on every network boot
>>ROM, a 1 minute delay on the SCSI controller before it even starts
>>scanning the bus, then another good 10 seconds before it starts booting.
>>Gets annoying after a few reboots..
>>
>>
>
>Indeed, the BIOS bootup time on servers is typically anywhere from
>really bad to truly awful.
>
>
>
I try *very* hard not to do bootup on servers, the paperwork involved
with an outage takes longer than the boot time ;-)
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-06-01 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` [git patch] libata resume fix Robert Hancock
2006-06-01 13:48 ` Jens Axboe
2006-06-01 14:20 ` Bill Davidsen [this message]
2006-06-06 6:54 ` Tejun Heo
2006-06-06 7:05 ` Jens Axboe
2006-06-06 7:10 ` Tejun Heo
2006-05-28 20:34 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
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
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=447EF7BE.1020005@tmr.com \
--to=davidsen@tmr.com \
--cc=axboe@suse.de \
--cc=hancockr@shaw.ca \
--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