From owner-freebsd-current Sun May 24 06:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13709 for freebsd-current-outgoing; Sun, 24 May 1998 06:04:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13702 for ; Sun, 24 May 1998 06:04:26 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id VAA16711; Sun, 24 May 1998 21:04:04 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805241304.VAA16711@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Thyer cc: Greg Lehey , FreeBSD current users Subject: Re: More about NFS problems under current In-reply-to: Your message of "Sat, 23 May 1998 19:03:00 +0930." <356697CC.E809D7C7@camtech.net.au> Date: Sun, 24 May 1998 21:04:03 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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