[8250] in linux-scsi channel archive
Re: domain validation
daemon@ATHENA.MIT.EDU (Robert Frey)
Fri Feb 25 19:09:30 2000
Message-ID: <38B70DF9.542B6AAF@home.com>
Date: Fri, 25 Feb 2000 15:19:21 -0800
From: Robert Frey <bobfrey@home.com>
MIME-Version: 1.0
To: "Justin T. Gibbs" <gibbs@FreeBSD.org>
Cc: Dan Jones <djones@valinux.com>,
Doug Ledford <dledford@redhat.com>, linux-scsi@vger.rutgers.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
"Justin T. Gibbs" wrote:
> I agree with all that you've said, but you've left out the most compelling
> reason that domain validation is necessary: SCSI->SCSI bridges. Although
> a SCSI-SCSI bridge may support some LVD transfer speeds, it may not support
> all of them. The only way to find out is to perform domain validation.
> For instance, I have no idea if the currently available LVD->SE/LVD bridges
> understand DT transfers.
That's a good point along with Dan's legacy SCSI backplane example. But I can
argue this is a misconfiguration. Why use a 160 MB/S drive in a system where it
will only run at 40 or 80 MB/S? In most systems I would expect this set-up to
be unintentional and the user would expect 160 MB/S performance. My point is in
a good domain validation implementation the end-user should be notified of the
under utilized drive instead of it being hidden.
Bob Frey
bobfrey@home.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
