From owner-freebsd-arch@FreeBSD.ORG Wed Nov 9 04:24:13 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 6E369106564A; Wed, 9 Nov 2011 04:24:13 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id C93518FC15; Wed, 9 Nov 2011 04:24:12 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id pA94BZJr087731; Wed, 9 Nov 2011 04:11:35 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.119] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id yqxpgapnzhavc8t4dgdftphb5w; Wed, 09 Nov 2011 04:11:35 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <20111109033504.GS6110@elvis.mu.org> Date: Tue, 8 Nov 2011 20:11:35 -0800 Content-Transfer-Encoding: 7bit Message-Id: <840E509B-0D63-41C2-B26A-31655F1D42C2@kientzle.com> 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> To: Alfred Perlstein X-Mailer: Apple Mail (2.1251.1) Cc: Bruce Cran , Ed Schouten , Jilles Tjoelker , arch@freebsd.org, freebsd-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: Wed, 09 Nov 2011 04:24:13 -0000 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