public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Kent Borg <kentborg@borg.org>
Cc: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	nick@snowman.net, Baldur Norddahl <bbn-linux-kernel@clansoft.dk>,
	Mike Dresser <mdresser_l@windsormachine.com>,
	linux-kernel@vger.kernel.org
Subject: Re: IDE/raid performance
Date: Wed, 17 Apr 2002 16:26:34 -0700	[thread overview]
Message-ID: <20020417232634.GC574@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0204171108480.3300-100000@ns> <E16xrfQ-0002VF-00@the-village.bc.nu> <20020417102722.B26720@vger.timpanogas.org> <20020417134716.D10041@borg.org>

On Wed, Apr 17, 2002 at 01:47:16PM -0400, Kent Borg wrote:
> 
> On Wed, Apr 17, 2002 at 10:27:22AM -0700, Jeff V. Merkey wrote:
> > From my analysis with 3Ware at 32 drive configurations, you really
> > need to power the drives from a separate power supply is you have 
> > more than 16 devices.  They really suck the power during initial 
> > spinup.
> 
> It seems an obvious help would be to have the option of spinning up
> the drives one at a time at 2-3 second intervals.  I know a fast drive
> doesn't get up to speed in 3 seconds, but the nastiest draw is going
> to be over by then.
> 
> A machine with 32 drives is pretty serious stuff and probably isn't
> booting in a few seconds anyway--another 60-some seconds might be a
> desirable option.
> 
> Does this exist anywhere?  Would it have to be a BIOS feature?

I doubt it.

All of the IDE drives I have used spin up when power is applied.  Most of
the scsi (except for some really old ones) have a jumper that tells the
drive to wait until it receives a message from the scsi controller to spin up.

I'd imagine that IDE would need some protocol spec changes before this could
be supported (at least a "spin the drive up" message...).

Mike

  parent reply	other threads:[~2002-04-17 23:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:58 IDE/raid performance Baldur Norddahl
2002-04-17 13:43 ` Mike Dresser
2002-04-17 14:00   ` Baldur Norddahl
2002-04-17 15:15     ` nick
2002-04-17 15:48       ` Alan Cox
2002-04-17 17:27         ` Jeff V. Merkey
2002-04-17 17:47           ` Kent Borg
2002-04-17 17:48             ` nick
2002-04-17 23:26             ` Mike Fedyk [this message]
2002-04-18  6:47               ` Andre Hedrick
2002-04-18  7:41               ` Helge Hafting
2002-04-18 21:22                 ` Mike Fedyk
2002-04-17 17:36       ` Baldur Norddahl
2002-04-17 17:41         ` Mike Dresser
2002-04-17 17:46         ` nick
2002-04-17 22:35         ` dean gaudet
2002-04-17 23:52           ` Alan Cox
2002-04-17 20:36       ` Kurt Garloff
2002-04-21 19:01         ` Pavel Machek
2002-04-18 15:51       ` Bill Davidsen
2002-04-18 18:33         ` Mike Galbraith
2002-04-17 15:09 ` Bill Davidsen
2002-04-17 18:38 ` Andre Hedrick
2002-04-17 22:44 ` Lincoln Dale
2002-04-18  0:38   ` Mike Fedyk

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=20020417232634.GC574@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bbn-linux-kernel@clansoft.dk \
    --cc=jmerkey@vger.timpanogas.org \
    --cc=kentborg@borg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdresser_l@windsormachine.com \
    --cc=nick@snowman.net \
    /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