From owner-freebsd-current@FreeBSD.ORG Sun May 8 13:09:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A76E816A4E2; Sun, 8 May 2005 13:09:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4616243D69; Sun, 8 May 2005 13:09:34 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j48DEgud021073; Sun, 8 May 2005 07:14:42 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <427E0F77.50006@samsco.org> Date: Sun, 08 May 2005 07:09:11 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steven Hartland References: <069901c54bfd$2967ba40$7f06000a@int.mediasurface.com> <427D5AA0.1080609@withagen.nl> <002b01c553be$93a5b790$b3db87d4@multiplay.co.uk> In-Reply-To: <002b01c553be$93a5b790$b3db87d4@multiplay.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Very low disk performance Highpoint 1820a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2005 13:09:34 -0000 Steven Hartland wrote: > If that where the case it would have been it wouldn't have been > 46Mb/s it would have been 543Mb/s, just tested it for you :P The RR1280 cards are really just software RAID cards. All of the parity calculations are done by the CPU. I couldn't find much evidence that the driver has parity routines that are optimized for the CPU, so it's likely doing a very inefficient job at it. Scott