From owner-freebsd-arch@FreeBSD.ORG Thu Apr 14 21:34:37 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E22A0106566B; Thu, 14 Apr 2011 21:34:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B86F28FC08; Thu, 14 Apr 2011 21:34:37 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 5283646B09; Thu, 14 Apr 2011 17:34:37 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D4A968A01B; Thu, 14 Apr 2011 17:34:36 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Date: Thu, 14 Apr 2011 17:08:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201104141708.32568.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 14 Apr 2011 17:34:36 -0400 (EDT) Cc: mdf@freebsd.org Subject: Re: posix_fallocate(2) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2011 21:34:38 -0000 On Thursday, April 14, 2011 3:35:34 pm mdf@freebsd.org wrote: > For work we need a functionality in our filesystem that is pretty much > like posix_fallocate(2), so we're using the name and I've added a > default VOP_ALLOCATE definition that does the right, but dumb, thing. > > The most recent mention of this function in FreeBSD was another thread > lamenting it's failure to exist: > http://lists.freebsd.org/pipermail/freebsd-ports/2010-February/059268.html > > The attached files are the core of the kernel implementation of the > syscall and a default VOP for any filesystem not supporting > VOP_ALLOCATE, which allows the syscall to work as expected but in a > non-performant manner. I didn't see this syscall in NetBSD or > OpenBSD, so I plan to add it to the end of our syscall table. > > What I wanted to check with -arch about was: > > 1) is there still a desire for this syscall? > 2) is this naive implementation useful enough to serve as a default > for all filesystems until someone with more knowledge fills them in? > 3) are there any obvious bugs or missing elements? Hmm, this would be good to have. Unfortunately the list manager software ate everything except the manpage. Can you post the patches at a URL? -- John Baldwin