From: Patrick Mansfield <patmans@us.ibm.com>
To: Shane Walton <dsrelist@yahoo.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Stream Lined Booting - SCSI Hold Up
Date: Thu, 6 Jun 2002 13:44:19 -0700 [thread overview]
Message-ID: <20020606134419.A24456@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <20020605172240.17081.qmail@web20808.mail.yahoo.com>
On Wed, Jun 05, 2002 at 10:22:40AM -0700, Shane Walton wrote:
> Good day,
>
> I work with US DoD systems, and one of my requirements
> is to boot an ix86 based system with an aic7xxx SCSI
> interface in 15 seconds. One of the apparent problems
> is the SCSI BIOS and aic7xxx driver take a long time
> to find one drive and then probe other empty channels.
> Is there a way to inform the aic7xxx driver of
> connected hardware to limit the initialization phase?
> Thanks for the help.
I never thought to disable the reset, getting rid of the SCSI resets
probably cuts 10-20 seconds off my boot time.
You can turn of the AIC driver reset, and shorten the selection timeout,
see linux/drivers/scsi/README.aic7xxx for details.
With my hardware, I can also disable the BIOS reset, and limit BIOS
scanning from the BIOS config screen (hit ctl-A during boot).
On my system, it saves me about 10 seconds to boot with:
lilo: linux-1 aic7xxx=no_reset aic7xxx=seltime:3
There are no options in linux scsi to limit the scanning of the target
id's or channels, I don't think there are any in the AIC driver either.
You could hack the driver and lower the max_id, and/or lower max_channel,
or somehow disable unused channels, but I doubt it will save much time
(7 id's * 2 channels * 32 ms/per-selection-timeout or so).
-- Patrick Mansfield
next prev parent reply other threads:[~2002-06-06 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 17:22 Shane Walton
2002-06-06 20:44 ` Patrick Mansfield [this message]
2002-06-07 22:55 ` Patrick Mansfield
2002-06-08 3:15 ` Justin T. Gibbs
2002-06-07 16:51 Shane Walton
2002-06-07 18:08 ` Kai Henningsen
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=20020606134419.A24456@eng2.beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=dsrelist@yahoo.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
all inboxes | Powered by JetHome®