From owner-freebsd-hackers Thu Apr 12 13:51:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id CF9A037B449 for ; Thu, 12 Apr 2001 13:51:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f3CKooC59190; Thu, 12 Apr 2001 22:50:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Rik van Riel , David Xu , freebsd-hackers@FreeBSD.ORG Subject: Re: vm balance In-Reply-To: Your message of "Thu, 12 Apr 2001 10:57:19 PDT." <200104121757.f3CHvJd20639@earth.backplane.com> Date: Thu, 12 Apr 2001 22:50:50 +0200 Message-ID: <59188.987108650@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200104121757.f3CHvJd20639@earth.backplane.com>, Matt Dillon writes: > Again, keep in mind that the namei cache is strictly throw-away, but > entries can often be reconstituted later by the filesystem without I/O > due to the VM Page cache (and/or buffer cache depending on > vfs.vmiodirenable). So as with the buffer cache and inode cache, > the number of entries can be limited without killing performance or > scaleability. Uhm, that is actually not true. We keep namecache entries around as long as we can use them, and that generally means that recreating them is a rather expensive operation, involving creation of vnode and very likely a vm object again. We can safely say that you cannot profitably _increase_ the size of the namecache, except for the negative entries where raw statistics will have to be the judge of the profitability of the idea. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message