From owner-freebsd-hackers@FreeBSD.ORG Fri May 13 06:21:10 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 903EA106566B; Fri, 13 May 2011 06:21:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3B08FC0A; Fri, 13 May 2011 06:21:10 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2d19:d22d:b020:7e1b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 0CA904AC1C; Fri, 13 May 2011 10:21:07 +0400 (MSD) Date: Fri, 13 May 2011 10:21:01 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <829202538.20110513102101@serebryakov.spb.ru> To: Jilles Tjoelker In-Reply-To: <20110512230327.GA82602@stack.nl> References: <1649118429.20110512113812@serebryakov.spb.ru> <20110512230327.GA82602@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Lev Serebryakov Subject: Re: Does FreeBSD have replacement for posix_fadvice() or fcntl(F_RDADVISE)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2011 06:21:10 -0000 Hello, Jilles. You wrote 13 =EC=E0=FF 2011 =E3., 3:03:27: >> It is like madvise(2) but for file descriptors. > An effect like POSIX_FADV_SEQUENTIAL can be obtained with the > F_READAHEAD or F_RDAHEAD fcntl(2) requests. The implementation is > divided between the generic VFS layer and various filesystems (cd9660, > ext2fs, msdosfs, nfs, xfs and ufs appear to use the information to some > degree). Does read ahead turned on by default (for UFS), as here is vfs.read_max? Or vfs.read_max is only "upper bound" for F_READAHEAD and it is turned off by default completely? --=20 // Black Lion AKA Lev Serebryakov