From owner-freebsd-hackers@FreeBSD.ORG  Sun Feb 12 12:25:16 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 57ED716A420
	for <freebsd-hackers@freebsd.org>; Sun, 12 Feb 2006 12:25:16 +0000 (GMT)
	(envelope-from davidt@yadt.co.uk)
Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D040043D49
	for <freebsd-hackers@freebsd.org>; Sun, 12 Feb 2006 12:25:15 +0000 (GMT)
	(envelope-from davidt@yadt.co.uk)
Received: from localhost (localhost [127.0.0.1])
	by outcold.yadt.co.uk (Postfix) with ESMTP id 3F3011DD4DC;
	Sun, 12 Feb 2006 12:25:14 +0000 (GMT)
Received: from outcold.yadt.co.uk ([127.0.0.1])
	by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 54317-02; Sun, 12 Feb 2006 12:25:13 +0000 (GMT)
Received: by outcold.yadt.co.uk (Postfix, from userid 1001)
	id BD8BA1DD4D9; Sun, 12 Feb 2006 12:25:13 +0000 (GMT)
Date: Sun, 12 Feb 2006 12:25:13 +0000
From: David Taylor <davidt@yadt.co.uk>
To: soralx@cydem.org
Message-ID: <20060212122513.GA58153@outcold.yadt.co.uk>
Mail-Followup-To: soralx@cydem.org, freebsd-hackers@freebsd.org
References: <200602112334.k1BNYf83084494@gate.bitblocks.com>
	<200602120127.03988.soralx@cydem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <200602120127.03988.soralx@cydem.org>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at yadt.co.uk
Cc: freebsd-hackers@freebsd.org
Subject: Re: RAID5 on athlon64 machines
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2006 12:25:16 -0000

On Sun, 12 Feb 2006, soralx@cydem.org wrote:
[missing attribution]
> >
> > You compute max data rates by considering the most optimistic
> > scenario, which is large sequetial writes.  For *this*
> > situation write rate will be higher than a single disk's.
> 
> How can the RAID5 write rate be higher for the whole array if not
> only it needs to write the data to all if its drives, but also
> compute and write a parity block?

Easy, you can write simultaneously to more than one drive, assuming
the drive was the bottleneck in the first place.

-- 
David Taylor