From owner-freebsd-arch@FreeBSD.ORG Fri Nov 4 17:47:52 2011 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 291B41065673; Fri, 4 Nov 2011 17:47:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 147FD8FC13; Fri, 4 Nov 2011 17:47:51 +0000 (UTC) Received: by elvis.mu.org (Postfix, from userid 1192) id 8BEE71A3D29; Fri, 4 Nov 2011 10:47:51 -0700 (PDT) Date: Fri, 4 Nov 2011 10:47:51 -0700 From: Alfred Perlstein To: Garrett Cooper Message-ID: <20111104174751.GH6110@elvis.mu.org> References: <201110281426.00013.jhb@freebsd.org> <201111011308.05204.jhb@freebsd.org> <4EB08740.8010601@cran.org.uk> <201111021136.12629.jhb@freebsd.org> <20111102202015.GQ6110@elvis.mu.org> <4EB2C9DD.9090606@FreeBSD.org> <20111104160319.GD6110@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Bruce Cran , Ed Schouten , Jilles Tjoelker , John Baldwin , arch@freebsd.org Subject: Re: [PATCH] fadvise(2) system call 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: Fri, 04 Nov 2011 17:47:52 -0000 * Garrett Cooper [111104 10:19] wrote: > On Nov 4, 2011, at 9:03 AM, Alfred Perlstein wrote: > > > * John Baldwin [111103 19:38] wrote: > >> On 11/2/11 1:20 PM, Alfred Perlstein wrote: > >>> * John Baldwin [111102 11:05] wrote: > >>>> On Tuesday, November 01, 2011 7:56:48 pm Bruce Cran wrote: > >>>>> On 01/11/2011 17:08, John Baldwin wrote: > >>>>>> I had found it via the web: http://linux.die.net/man/2/fadvise > >>>>>> However, after further searching it appears to be stale (if you follow > >>>>>> it's cross-reference to madvise(2), that page only has links to > >>>>>> posix_fadvise() and not fadvise()). > >>>>> > >>>>> There's > >>>>> http://www.speedware.com/HPe3000_resources/MPE_to_HP-UX_cross- > >>>> reference/system_administration_cross-reference/cmd.html?cmdid=MS_1800 > >>>>> for HP-UX ("*fadvise()* was derived by HP from the IEEE POSIX > >>>>> 1003.1-2001 Standard"), though it also has posix_fadvise. > >>>> > >>>> Hmm, that one actually has an extra argument. I'll just go with > >>>> posix_fadvise() for now. Interesting that HP lets you OR together > >>>> two policies (so you can say both "I will access this file sequentially > >>>> and with noreuse"). > >>> > >>> Makes sense for gzip/tar. > >> > >> Ehh, quite possibly not for something that generic. I think you only > >> want to do this if you have very specific knowledge about your access > >> pattern, and I do not think they are generically applicable. > > > > You often spend time untarring the same tarball over and over > > in your workflow John? > > This is starting to sound like something that libarchive / pkg_install would benefit from (jkh pkg_install or pkgng). > -Garrett It seems a no brainer to flip the bit on when reading an archive that's as large as main memory. It's annoying to untar something, then have my box have to page back in all programs. -- - Alfred Perlstein .- VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10 .- FreeBSD committer