From owner-freebsd-arch  Tue Feb 13 18:42:13 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id 1234637B503
	for <arch@FreeBSD.ORG>; Tue, 13 Feb 2001 18:42:11 -0800 (PST)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA05280;
	Wed, 14 Feb 2001 13:41:56 +1100
Date: Wed, 14 Feb 2001 13:41:30 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@besplex.bde.org
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Doug Rabson <dfr@nlsystems.com>, arch@FreeBSD.ORG
Subject: Re: sparse core dumps
In-Reply-To: <xzpsnliy9h4.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.21.0102141336490.1018-100000@besplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 13 Feb 2001, Dag-Erling Smorgrav wrote:

> Doug Rabson <dfr@nlsystems.com> writes:
> > Probably it should just use getpagesize() to decide what block size to
> > use.
> 
> Why not just hardcode PAGE_SIZE like I did? An incorrect value will
> still work, just slightly less efficiently. Empirical tests show that
> as long as you stick to reasonable values, the block size doesn't
> affect disk usage much.

One reason is that it is a bug for PAGE_SIZE to be visible to applications.

Bruce



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message