From owner-freebsd-current@FreeBSD.ORG Fri Jan 4 12:48:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D998116A419; Fri, 4 Jan 2008 12:48:44 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAA213C468; Fri, 4 Jan 2008 12:48:44 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 52D3220BB; Fri, 4 Jan 2008 13:48:36 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 3E62620B9; Fri, 4 Jan 2008 13:48:36 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 1B7CD844CD; Fri, 4 Jan 2008 13:48:36 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Robert Watson References: <477C82F0.5060809@freebsd.org> <863ateemw2.fsf@ds4.des.no> <20080104002002.L30578@fledge.watson.org> <86bq81c12d.fsf@ds4.des.no> <20080104111938.N77222@fledge.watson.org> <20080104113426.T77222@fledge.watson.org> Date: Fri, 04 Jan 2008 13:48:36 +0100 In-Reply-To: <20080104113426.T77222@fledge.watson.org> (Robert Watson's message of "Fri\, 4 Jan 2008 11\:38\:23 +0000 \(GMT\)") Message-ID: <86ir29ah97.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Jason Evans , Igor Mozolevsky Subject: Re: sbrk(2) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2008 12:48:44 -0000 Robert Watson writes: > As I mentioned in my e-mail, it would be nice if our file system > supported a way to reserve blocks for files without hooking them up to > the file's visiible address space (in order to avoid zeroing them, > which is required if you do want to hook them up for an unprivileged > process). However, that feature doesn't currently exist. Even for files which are intended to be filled up immediately, telling the file system ahead of time how much data will be written would allow it to make much better layout decisions. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no