From owner-freebsd-hackers Tue Dec 7 16:52:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 9B59C14C38 for ; Tue, 7 Dec 1999 16:52:29 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id TAA18913; Tue, 7 Dec 1999 19:51:43 -0500 (EST) Reply-To: Randell Jesup To: freebsd-hackers@freebsd.org, Matthew Dillon Subject: Re: ELF & putting inode at the front of a file From: Randell Jesup Date: 07 Dec 1999 19:53:51 -0500 In-Reply-To: Matthew Dillon's message of "Mon, 6 Dec 1999 16:46:36 -0800 (PST)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: >:> distribute the inodes all over the cylinder group rather then concentrate >:> all the inodes in one place. >: >:Yes. I have implemented most of the code. I noticed the "ls -al" is slow >:but "ls" is OK. > > Yes, ls (without any options) is ok because the file type is now being > stuffed in the directory entry, allowing ls (without any options) to > avoid stat()ing the file. Interesting - I made a similar mechanism in a hash-chain-based filesystem to speed up directory listings; by storing all the commonly accessed information about a file in the directory in a compressed format, thus avoiding fetching the fileheader (inode) block for every file. The speedup was impressive; I think I was getting 7-25 entries per 512-byte sector; including just all ls -l information. The downside was increased overhead on file-close-after-modify and create/delete, but not a lot. As a side-benefit, recovery after a trashed FS is slightly easier since there's more redundant information available (if the main directory sector/inode gets whacked). -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message