Date: Tue, 19 Aug 2003 12:25:11 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Munehiro Matsuda <haro@h4.dion.ne.jp> Cc: current@freebsd.org Subject: Re: DEVFS related message Message-ID: <46803.1061288711@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 14 Aug 2003 20:56:49 %2B0900." <20030814.205649.71088058.haro@h4.dion.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030814.205649.71088058.haro@h4.dion.ne.jp>, Munehiro Matsuda writ es: >Hi All, > >I just got following DEVFS related message with >this mornings current. > >DEVFS Overflow table with 32768 entries allocated when 925 in use > >Anybody seen this? This is mostly harmless. When DEVFS initially was integrated the locking situation was rather tricky and malloc failures therefor not easy to handle. Therefore DEVFS uses a compile time array of pointers to its inodes. If this table seems to be running out, (less than 100 free entries) an "overflow" table will be attempted allocated which can contain more entries. You can adjust both the regular and the overflow table sizes with compile time constants NDEVFSINO and NDEVFSOVERFLOW. When more of the kernel has been de-Giantized, this code can be revisited and these constants can probably be eliminated. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46803.1061288711>