Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Oct 2010 07:35:21 -0700
From:      Matthew Jacob <mj@feral.com>
To:        freebsd-hackers@freebsd.org
Subject:   Re: SCSI_DELAY cleanup
Message-ID:  <4CBDACA9.3040701@feral.com>
In-Reply-To: <20101019143110.GA5802@freebsd.org>
References:  <20101018235318.GA87158@freebsd.org> <4CBCE67C.1070106@feral.com>	<20101019103432.GA69208@freebsd.org> <4CBDA371.4080801@feral.com> <20101019143110.GA5802@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
  I'd go for the gusto in -current, but it's ok to be conservative too.

> On Tue Oct 19 10, Matthew Jacob wrote:
>>   It would be an effective behavioral change for those of us who remove
>> that line.
>> Personally, I think 5 seconds is too long- even 2 seconds is more than
>> adequate even for moderately old 'other' hardware like scanners.
>>
>> For -current, why don't you simply remove all of the config lines and
>> leave the default at 2000ms?
> hmmm...i can only test the delay value on amd64. i was under the impression
> that archs like arm and mips need the longer delay.
>
> also at some locations in the code SCSI_DELAY is being set to 15000. i believe
> this is the case when certain drivers (cam, ahb, aha) get loaded as a kernel
> module, but i'm not sure. it looks like this:
>
> .if !defined(KERNBUILDDIR)
> opt_scsi.h:
> 	echo "#define SCSI_DELAY 15000">  ${.TARGET}
> .endif
>
> cheers.
> alex
>
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CBDACA9.3040701>