From owner-freebsd-isp  Mon Aug 26 08:09:05 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA18133
          for isp-outgoing; Mon, 26 Aug 1996 08:09:05 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA18124
          for <freebsd-isp@FreeBSD.org>; Mon, 26 Aug 1996 08:09:02 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA00291; Mon, 26 Aug 1996 10:07:49 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199608261507.KAA00291@brasil.moneng.mei.com>
Subject: Re: Anyone using ccd (FreeBSD disk striper) for news
To: michael@memra.com (Michael Dillon)
Date: Mon, 26 Aug 1996 10:07:48 -0500 (CDT)
Cc: freebsd-isp@FreeBSD.org, craigs@OS.COM
In-Reply-To: <Pine.BSI.3.93.960822160048.14970N-100000@sidhe.memra.com> from "Michael Dillon" at Aug 22, 96 04:03:27 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-isp@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> On Thu, 22 Aug 1996, Joe Greco wrote:
> 
> > Use a large stripe size.  I use 1 cylinder group.  You are not striping for
> > bandwidth.  You are striping for CONCURRENCY.  You _want_ one mechanism to
> > be able to handle an _entire_ file access on its own.
> 
> By concurrency do you mean that the write requests are non-blocking and
> thus a request that lands on a second drive can start writing before a
> previous request completes?

Perhaps more importantly, *reads*.

> And did you need to fo that tweak to UFS meta data updates that makes it
> more like Linux's ext2fs?

I've played with metadata updates before (disabled ATIME and MTIME updates)
but I don't want to do it on a production system until there is an
officially sanctioned method to do so.

... JG