From owner-freebsd-hackers Thu Jul 22 15:45:56 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 B0C301563B for ; Thu, 22 Jul 1999 15:45:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA05097; Thu, 22 Jul 1999 15:44:07 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Jul 1999 15:44:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199907222244.PAA05097@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222237.SAA81150@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have 2 NFS servers. One is primarily read-only, the other read-write, they :service the same clients (the read-only services more). They are (were) of :the same build. I have a problem on the read/write server where it chews :through mbuf clusters (it goes through about 3k in a day). Especially late :at night the machine is not busy. And now it is also not busy, yet every :minute or so it goes through a few mbuf clusters. The rate is about 108 :minutes for 300 clusters. Does it sound reasonable that there is a mbuf leak :in the NFS code somewhere? : :-- :David Cross | email: crossd@cs.rpi.edu The server side caches mbuf chains to hold replies to NFS requests. This is done because it is quite common for requests to be repeated. The question is whether you are simply seeing the effect of this caching, or whether you have an actual mbuf leak. Does the mbuf usage / memory usage stabilize after a while or do you actually run out? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message