Date: Mon, 1 Nov 1999 10:13:35 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: freebsd-arch@freebsd.org Subject: Re: Storing small files in inodes Message-ID: <99Nov1.100916est.40382@border.alcanet.com.au> In-Reply-To: <19991029150228.BB45314BF7@hub.freebsd.org> References: <99Oct29.085056est.40332@border.alcanet.com.au> <19991029150228.BB45314BF7@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Oct-30 01:02:28 +1000, Jonathan M. Bresler wrote: >http://www.usenix.org/publications/library/proceedings/ana97/ganger.html > >With embedded inodes, the inodes for most files are stored in the >directory with the corresponding name, removing a physical level of >indirection without sacrificing the logical level of indirection. With >explicit grouping, the data blocks of multiple small files named by a >given directory are allocated adjacently and moved to and from the >disk as a unit in most cases. C-FFS is a more radical change than I was thinking of. By moving the inodes into the directory, it needs special handling for files don't have exactly 1 link. Also, from my reading of the paper, a small file still occupies a complete data block, it's just that the data block is `close to' the directory entry/inode for the file. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Nov1.100916est.40382>