From owner-freebsd-amd64@FreeBSD.ORG  Tue Dec 23 05:23:50 2003
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 609C016A4CE
	for <freebsd-amd64@freebsd.org>; Tue, 23 Dec 2003 05:23:50 -0800 (PST)
Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com
	[24.73.246.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B4A0543D3F
	for <freebsd-amd64@freebsd.org>;
	Tue, 23 Dec 2003 05:23:47 -0800 (PST)
	(envelope-from james@bigtex.jrv.org)
Received: from bigtex.jrv.org (localhost [127.0.0.1])
	by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id hBNDNlo8025850
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <freebsd-amd64@freebsd.org>; Tue, 23 Dec 2003 07:23:47 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id hBNDNlFK025847;
	Tue, 23 Dec 2003 07:23:47 -0600 (CST)
Date: Tue, 23 Dec 2003 07:23:47 -0600 (CST)
Message-Id: <200312231323.hBNDNlFK025847@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: freebsd-amd64@freebsd.org
Subject: bounce buffer statistics?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2003 13:23:50 -0000

Are there any sysctl variables that report the number of bounce-buffer
related copies that the kernel must make due to limited address ranges
of devices?

I have 8 GB of RAM and a 32-bit sATA controller than can't directly
address memory above 4 GB.  I'm wondering how much that is really
hurting.