From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikita Danilov Subject: Re: [PATCH] [Request for inclusion] Filesystem in Userspace Date: Wed, 17 Nov 2004 20:58:42 +0300 Message-ID: <16795.37202.793499.93514@gargle.gargle.HOWL> References: <84144f0204111602136a9bbded@mail.gmail.com> <20041116120226.A27354@pauline.vellum.cz> <20041116163314.GA6264@kroah.com> <16795.33515.187015.492860@thebsh.namesys.com> <16795.35688.634029.21478@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Miklos Szeredi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: To: Jan Engelhardt In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Jan Engelhardt writes: > > > >mount -tfoo_ctrlfs -o host=/mnt/point /mnt/control-point > > > > > > Looks to me like a pollution of the mount table if you do this on a lot of > > > filesystems. > > > >If you have a lot of file-systems your mount table is already polluted. > > That does not justify to pollute with *_ctlfs it > to double the size it already is. "mount-table" (fs/namespace.c:mount_hashtable) is consulted only when path-resolution crosses dentry marked as mount-point (has non-zero ->d_mounted field), which is rare, and this means that number of elements in mount_hashtable has little effect on the cost of path-name resolution. Unless, of course, by "polluted" you mean that output of "cat /proc/self/mounts" becomes longer. Nikita.