Date: Sun, 24 May 1998 21:04:03 +0800 From: Peter Wemm <peter@netplex.com.au> To: Matthew Thyer <thyerm@camtech.net.au> Cc: Greg Lehey <grog@lemis.com>, FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: More about NFS problems under current Message-ID: <199805241304.VAA16711@spinner.netplex.com.au> In-Reply-To: Your message of "Sat, 23 May 1998 19:03:00 %2B0930." <356697CC.E809D7C7@camtech.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Thyer wrote: > It's happening to me. > > Greg Lehey wrote: > > > > I haven't been able to get my NFS to work reliably yet, but I noticed > > the following message while booting: > > > > struct nfsmount bloated (> 512bytes) > > Try reducing NFS_MUIDHASHSIZ > > > > I don't know to what extent that is related, but I suppose it's worth > > trying. Presumably this is happening to everybody. Question: > > NFS_MUIDHASHSIZ is currently 63. Should I reduce it to 31, or is the > > value not used as a mask? > > > > Greg > > -- > > See complete headers for address and phone numbers > > finger grog@lemis.com for PGP public key This is harmless. If you've got NFS problems, it's not because of this. This is a courtesy warning that certain large structure has gone over a convenient power-of-two size, and that means that we get a large (nearly 0.5KB) block of "lost" space. Since we're malloc'ing a 544 byte struct, malloc assigns a 1024 byte block. Quite harmless, and generally not a problem unless you've got more than a few hundred NFS mounts to other servers. I've changed my copy to use the zone allocator for space efficiency, but on the downside, it can use up a 4K page for a single 544byte nfsmount struct. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805241304.VAA16711>