Date: Thu, 03 Nov 2011 10:05:33 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: Bruce Cran <bruce@cran.org.uk>, Ed Schouten <ed@80386.nl>, Jilles Tjoelker <jilles@stack.nl>, arch@freebsd.org Subject: Re: [PATCH] fadvise(2) system call Message-ID: <4EB2C9DD.9090606@FreeBSD.org> In-Reply-To: <20111102202015.GQ6110@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/2/11 1:20 PM, Alfred Perlstein wrote: > * John Baldwin<jhb@freebsd.org> [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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB2C9DD.9090606>