From owner-freebsd-hackers Sun Feb 4 20:11:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28710 for hackers-outgoing; Sun, 4 Feb 1996 20:11:29 -0800 (PST) Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA28647 for ; Sun, 4 Feb 1996 20:09:29 -0800 (PST) Received: from localhost (babkin@localhost) by hq.icb.chel.su (8.6.5/8.6.5) id IAA24118; Mon, 5 Feb 1996 08:50:20 +0500 From: "Serge A. Babkin" Message-Id: <199602050350.IAA24118@hq.icb.chel.su> Subject: Re: FAT filesystem performance To: terry@lambert.org (Terry Lambert) Date: Mon, 5 Feb 1996 08:50:19 +0500 (GMT+0500) Cc: luigi@labinfo.iet.unipi.it, hackers@FreeBSD.org In-Reply-To: <199602042148.OAA06143@phaeton.artisoft.com> from "Terry Lambert" at Feb 4, 96 02:48:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org Precedence: bulk > > We use FAT filesystems both in the kernel, and in mtools. > > For the latter, I thought there was a quick fix to the problem of > > caching the FAT: just mmap the device, and the kernel will do caching > > for you. Well, it does not look that simple, as the vast majority of > > raw devices does not support mmap. > > > > I am wondering: how hard would it be to add mmap() to, say, wd.c ? > > Would it have other useful applications ? > > This would be useful for mtools, but not for the kernel version of FAT. > > The FAT-caching in the MACH implementation (you *could* just port the > MACH code...) takes a significant amount of memory, IMO. Hmm... FAT can contain at most 64K of entries, each 2 bytes long, so the needed amount of memory (if you cache raw FAT and don't try to make any ``cooked'' version) must be at most 128Kbytes long. IMHO the raw FAT is enough convenient ant takes not very much of memory. -SB