From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 19:44:15 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C43E1065863 for ; Mon, 2 Mar 2009 19:44:15 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id D32FE8FC0A for ; Mon, 2 Mar 2009 19:44:14 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n22JiAUq078813; Mon, 2 Mar 2009 12:44:11 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <49AC370A.1040700@samsco.org> Date: Mon, 02 Mar 2009 12:44:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Josh Paetzel References: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> In-Reply-To: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: twa driver and 3ware 9690SA issues X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 19:44:17 -0000 Josh Paetzel wrote: > This is somewhat of a repost from questions@, and I'm currently engaged > with 3ware about this issue. > > I have several 3ware 9690SA SAS RAID controllers. This item is very > similar to their 9650SE controller. It uses the same firmware and > driver, the difference being it can handle SAS drives. Up until this > point all of the arrays we've used with these drives have been RAID 1 > arrays with 7200 RPM SATA drives, but recently we've started using > 15,000 MBA series Fujitsu SAS drives in places. > > The arrays have always been detected as: > > da0: Fixed Direct Access SCSI-5 device > da0: 100.000MB/s transfers This 100.000MB/s number is fictitious. The driver is just filling in a dummy value. Filling in the real number would require the driver being able to query the card for the negotiated bus speed. I have no idea if that's possible for TWA given the programming information that is public for the card. > > Which wasn't that much of an issue, as SATA drives aren't capable of > sustained sequential 100 MB/sec transfers anyways, but the SAS drives we > are getting are supposedly capable of 180 Megs/sec and I'm not seeing > it. I'm unsure of how to eliminate caching from the equation, simple > tests like dd if=/dev/zero of=testfile bs=8m count=1000 seem to support > what dmesg reports by returning 96 Meg/sec transfer rates > FreeBSD limits individual I/O segments through the CAM subsystem to 64K. It can safely be raised to 128K via some patches that I have, and you will see a corresponding improvement in performance. I don't believe that it can be safely raised above that for the TWA controllers. Scott