From owner-freebsd-arch Thu Oct 28 15:41: 3 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 995C614C39 for ; Thu, 28 Oct 1999 15:41:00 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id AAA04258 for ; Fri, 29 Oct 1999 00:40:59 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA35488 for freebsd-arch@freebsd.org; Fri, 29 Oct 1999 00:40:57 +0200 (MET DST) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3799E14C39 for ; Thu, 28 Oct 1999 15:40:46 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Fri, 29 Oct 1999 08:35:37 +1000 Content-return: prohibited Date: Fri, 29 Oct 1999 08:40:38 +1000 From: Peter Jeremy Subject: Re: Storing small files in inodes In-reply-to: <199910281926.MAA25987@kithrup.com> To: freebsd-arch@freebsd.org Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct29.083537est.40336@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii 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> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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