From owner-freebsd-hackers Fri Jul 23 9: 7: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 22C8114CAB for ; Fri, 23 Jul 1999 09:07:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA25958; Fri, 23 Jul 1999 09:06:01 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 09:06:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199907231606.JAA25958@apollo.backplane.com> To: Doug Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222246.SAA81283@cs.rpi.edu> <37980EBC.C38668E1@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :"David E. Cross" wrote: :> :> Well, I just -STABLED the server to see if it fixed it, but I was certainly :> running out. the server had only 3000-ish mbuf chains, and it would go through :> them all in a day. : : Well, have you tried increasing the number of available mbufs and see if :you reach a point of stability? Assuming you have enough physical ram you :could do 15k mbufs on -Stable without a problem. Check LINT for the :nmbclusters option if you need help with it. : :Good luck, : :Doug Well, the cache shouldn't eat up *that* many mbufs! The problem is likely to be real. There is a good chance the leakage is in nfs_serv.c, which I fixed for -current. I do not think those changes have been backported to -STABLE. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message