From owner-freebsd-hackers Thu Jan 30 22:49:12 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F27B37B401 for ; Thu, 30 Jan 2003 22:49:11 -0800 (PST) Received: from mx9.mail.ru (mx9.mail.ru [194.67.57.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21F5E43F43 for ; Thu, 30 Jan 2003 22:49:10 -0800 (PST) (envelope-from shmukler@mail.ru) Received: from f13.int ([10.0.0.105] helo=f13.mail.ru) by mx9.mail.ru with esmtp (Exim MX.9) id 18eUz6-0004ZC-00 for freebsd-hackers@freebsd.org; Fri, 31 Jan 2003 09:49:08 +0300 Received: from mail by f13.mail.ru with local (Exim FE.1) id 18eUz6-0001D0-00 for freebsd-hackers@freebsd.org; Fri, 31 Jan 2003 09:49:08 +0300 Received: from [216.194.2.239] by win.mail.ru with HTTP; Fri, 31 Jan 2003 09:49:08 +0300 From: "Igor Shmukler" To: freebsd-hackers@freebsd.org Subject: Re: Random disk cache expiry Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [216.194.2.239] Date: Fri, 31 Jan 2003 09:49:08 +0300 Reply-To: "Igor Shmukler" Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > You have found an optimal replacement algorithm for the case of > repeated sequential reads. In fact, if you know in advance what > the access pattern is going to be, it is *always* possible to find > an optimal replacement algorithm. Specifically, you always > replace the block in the cache that will not be used for the > longest time in the future. Did everyone read UBM paper from OSDI? It presents one possible solution for dealing with sequentaly accessed files. Why is it not enough (at least to begin with)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message