Date: Tue, 8 Nov 2011 20:11:35 -0800 From: Tim Kientzle <tim@kientzle.com> 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, freebsd-arch@freebsd.org Subject: Re: [PATCH] fadvise(2) system call Message-ID: <840E509B-0D63-41C2-B26A-31655F1D42C2@kientzle.com> In-Reply-To: <20111109033504.GS6110@elvis.mu.org> References: <201110281426.00013.jhb@freebsd.org> <4EB2C9DD.9090606@FreeBSD.org> <20111104160319.GD6110@elvis.mu.org> <201111080800.32717.jhb@freebsd.org> <20111109033504.GS6110@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 8, 2011, at 7:35 PM, Alfred Perlstein wrote: > > One other optimization would be to set the bit when tar or other such apps > notice that the file exceeds the memory of the system, effectively noting > that it would be blowing out the entire cache. Tar does not know the amount of RAM in the system nor the size of the cache. It definitely does not know how the kernel caching policies interact with any particular access pattern. It should be able to provide hints to the kernel about the likely access pattern, though. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?840E509B-0D63-41C2-B26A-31655F1D42C2>