From owner-freebsd-current Thu Sep 17 13:41:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23438 for freebsd-current-outgoing; Thu, 17 Sep 1998 13:41:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23297 for ; Thu, 17 Sep 1998 13:41:03 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA05178; Thu, 17 Sep 1998 14:40:29 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809172040.OAA05178@panzer.plutotech.com> Subject: Re: LINT not up to date In-Reply-To: <19980917132254.B4420@nuxi.com> from David O'Brien at "Sep 17, 98 01:22:54 pm" To: obrien@NUXI.com Date: Thu, 17 Sep 1998 14:40:29 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote... > > > > options SCSI_DELAY=8000 # Be pessimistic about Joe SCSI device > ... > > #error "SCSI_DELAY is in milliseconds, not seconds! Please use a larger value" > > I am kinda wondering why this gratuitous change even took place. Couldn't > the *software* made the conversion? Why the change on the user interface > (of kernel building)? It isn't "gratuitous" at all. The bus settle delay affects more than just booting, it also affects how long we freeze the SIM queue after a bus reset and how long we freeze a device queue after a BDR. Some folks may have devices that don't need really long bus settle delay, and may not want their machines hung for a second after a BDR or bus reset. We could have changed the option name, which would be an interface change. Kernel building "interfaces", if you can call them that, change all the time. We've already changed a number of them in the CAM switchover. > People thing easily in seconds. Not so well in milliseconds. I could > see someone getting confused on how many millisecs in a second and use > "800" which would fly under your radar, but be even quicker than the > default. (it's not too late to change back... :)) I don't think it'll turn out to be a big problem, really. If folks can't figure out how many milliseconds are in a second, I question what they're doing using a computer in the first place, much less FreeBSD. :) If enough people are really upset about this, we can make it something like CAM_BUS_SETTLE_DELAY instead. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message