Date: Wed, 3 May 2000 17:33:18 +0700 (ALMST) From: Boris Popov <bp@butya.kz> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: A proposal : IFS Message-ID: <Pine.BSF.4.10.10005031717190.71327-100000@lion.butya.kz> In-Reply-To: <20000503040431.B53701@ewok.creative.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 May 2000, Adrian Chadd wrote: > I've had a modification to FFS called IFS (inode filesystem) in the works > for a while, and I think its time for people to look at it. In a nutshell, > it removes the directory namespace from FFS and presents a flat inode No, it just provides another namespace and eliminates the need of directory metadata. > numbered namespace to applications. It was originally written for > squid and inn type applications, but a few people have suggested other > applications such as CODA/AFS stores/caches, and temp filesystems. As I can see, the primary goal of IFS is to reduce cost of inode lookup operation. And no doubt the best method is to expose inode numbers directly to application. However it is not clear to me how applications will interact with IFS and working example (patches for squid) would be very useful. Some performance benchmarks are also appreciated. > The only things this code is lacking is support for NFS cookies, and > softupdates. I don't think either are very important right now, but I'm doubt that someone will need to export IFS via NFS. And softupdates are not important too in this case. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10005031717190.71327-100000>