From owner-cvs-all Wed Oct 24 1:11:40 2001 Delivered-To: cvs-all@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E734937B407; Wed, 24 Oct 2001 01:11:33 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9O8BRG94627; Wed, 24 Oct 2001 01:11:27 -0700 (PDT) (envelope-from dillon) Date: Wed, 24 Oct 2001 01:11:27 -0700 (PDT) From: Matthew Dillon Message-Id: <200110240811.f9O8BRG94627@apollo.backplane.com> To: Peter Pentchev Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/coda coda_subr.c src/sys/fs/msdosfs msdosfs_vfsops.c src/sys/fs/nwfs nwfs_vfsops.c src/sys/fs/smbfs smbfs_vfsops.c src/sys/fs/unionfs union_vfsops.c src/sys/gnu/ext2fs ext2_vfsops.c src/sys/kern vfs_subr.c ... References: <200110230121.f9N1LTa24181@freefall.freebsd.org> <20011024102305.A65744@straylight.oblivion.bg> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Would not an MFC of this break binary compatibility for fs-like modules, :like, badly? : :G'luck, :Peter I don't know of any binary-only FS kld's but even if there are a few I don't see any other way of implementing the kern.maxvnodes limits cleanly. I floated the patchset a while back, which you can examine at: http://apollo.backplane.com/FreeBSD4/maxvnodes-03.diff Considering the price of ram we've started to receive reports from various sources (not just Yahoo) of serious memory-related scaleability issues. Once you load 2G+ into a machine -stable starts to overload the vnode cache (mainly when dealing with a large number of small files), which can result in a machine panic. The cleanest way to fix it is to enforce kern.maxvnodes and the cleanest way to enforce kern.maxvnodes is to arrange in the vnodes in an LRU list under the mount structure. That means changing the existing list from LIST to TAILQ. We might have to go a step further to solve additional latency issues with sync - by turning the one vnode list into two lists: a clean and a dirty list. However, before I explore that possibility I am comitting the fast-loop fixes discussed in hackers. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message