Date: Fri, 29 Oct 1999 08:40:38 +1000 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: freebsd-arch@freebsd.org Subject: Re: Storing small files in inodes Message-ID: <99Oct29.083537est.40336@border.alcanet.com.au> In-Reply-To: <199910281926.MAA25987@kithrup.com> References: <99Oct28.135145est.40328@border.alcanet.com.au> <3.0.6.32.19991028081210.0079b7a0.kithrup.freebsd.freebsd-arch@192.168.255.1> <199910281926.MAA25987@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Oct-29 05:26:40 +1000, Sean Eric Fagan wrote: >And we're _already_ doing it for a particular class of files -- symlinks. Though symlinks are much easier to handle - you can only create them, read them and delete them. You can't update or mmap them. > My >only concern is that I'd like an option to disable it on a per-filesystem >basis. I suspect this would have to be a newfs option. To be able to use tunefs to enable/disable it would imply supporting both types of files within the same filesystem - which further implies a bit in the inode, or relying on the content of di_blocks. I believe we would need a new format (FS_??INODEFMT) in fs_inodefmt, which indicates that that all short files are stored in the inode. The length of the files could be indicated either by overloading (and possibly renaming) fs_maxsymlinklen or adding a new `fs_maxshortfile' which represents the same value as fs_maxsymlinklen. 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?99Oct29.083537est.40336>