From owner-freebsd-fs@FreeBSD.ORG  Sun Jul  6 13:05:59 2003
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 092B437B401
	for <freebsd-fs@freebsd.org>; Sun,  6 Jul 2003 13:05:59 -0700 (PDT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8C0164402D
	for <freebsd-fs@freebsd.org>; Sun,  6 Jul 2003 13:05:58 -0700 (PDT)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 678F72ED436; Sun,  6 Jul 2003 13:05:58 -0700 (PDT)
Date: Sun, 6 Jul 2003 13:05:58 -0700
From: Alfred Perlstein <bright@mu.org>
To: Trent George <soundsampler@sbcglobal.net>
Message-ID: <20030706200558.GG72093@elvis.mu.org>
References: <20030706190733.67131.qmail@web80010.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030706190733.67131.qmail@web80010.mail.yahoo.com>
User-Agent: Mutt/1.4.1i
cc: freebsd-fs@freebsd.org
Subject: Re: Software Disk Cache Limit Issues
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jul 2003 20:05:59 -0000

* Trent George <soundsampler@sbcglobal.net> [030706 12:07] wrote:
> Hi, 
>  
> I have a couple of questions. I have been experimenting with freebsd to provide similar functionality to netware's large write-back disk caching.

This is cool, thanks for the feedback.  Have you tried raising the
sysctl tunable for 'hirunningspace'?  That may alleviate some of the
issue.