From owner-freebsd-fs Mon Dec 6 14:30: 7 1999 Delivered-To: freebsd-fs@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 4B8B314FEB; Mon, 6 Dec 1999 14:29:54 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA06876; Mon, 6 Dec 1999 17:29:32 -0500 (EST) Date: Mon, 6 Dec 1999 16:16:32 -0500 (EST) From: Zhihui Zhang To: "Ronald G. Minnich" Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: ELF & putting inode at the front of a file In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Dec 1999, Ronald G. Minnich wrote: > On Mon, 6 Dec 1999, Zhihui Zhang wrote: > > I am doing some research on filesystem. I guess it may be faster to put > > the disk inode with its file data together so that both can be read into > > memory in one I/O. > > I still don't get it. To get the file, you do a lookup. So the inode is in > memory. The you call the handler for the executable. But the inode is in > memory at this point .... what am I missing? > When you read the disk inode, the first part of the data of its corresponding file is brought into the memory at the same time. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message