From owner-freebsd-fs Fri Jul 19 06:39:40 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26270 for fs-outgoing; Fri, 19 Jul 1996 06:39:40 -0700 (PDT) Received: from ccs.sogang.ac.kr (ccs.sogang.ac.kr [163.239.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26252 for ; Fri, 19 Jul 1996 06:39:36 -0700 (PDT) Received: from cslsun10.sogang.ac.kr by ccs.sogang.ac.kr (8.7.5/Sogang) id WAA09921; Fri, 19 Jul 1996 22:36:43 +0900 (KST) Received: by cslsun10.sogang.ac.kr (4.1/SMI-4.1) id AA05500; Fri, 19 Jul 96 22:38:45 KST From: heo@cslsun10.sogang.ac.kr (Heo Sung Gwan) Message-Id: <9607191338.AA05500@cslsun10.sogang.ac.kr> Subject: RE: RE:About buffer cache To: freebsd-fs@FreeBSD.ORG Date: Fri, 19 Jul 1996 22:38:44 +0900 (KST) Content-Type: text Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think that UNIX file system with buffer cache is not proper to support multimedia files(e.g mpeg files) becasue buffer cache is based on locality of referece(i.e. the recently referened block have high probabiliey to be referenced again). But multimedia files are accessed sequentially and therefore caching of the referenced block is not suitable and the block of mpeg file referenced by a process has low probability to be accessed by the other processes. So I think a FIFO buffer per each open file and the read-ahead to each FIFO buffer are good choice for multimedia file retrieval. In fact the many filesystems for multimedia adopted this approach( e.g. UC Berkeley CMFS). And there are two possible approaches: 1. Modification of buffer cache to FIFO buffers dynamically allocated. 2. User-level process that manages that FIFO buffers that access files through raw disk without buffer cache. Thanks for your resposes. Heo Sung-Gwan --- E-mail : heo@cslsun10.sogang.ac.kr