From owner-freebsd-stable Tue Jul 16 8: 0:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEBF937B401 for ; Tue, 16 Jul 2002 08:00:53 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171D643E5E for ; Tue, 16 Jul 2002 08:00:53 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA13962; Tue, 16 Jul 2002 11:00:52 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6GF0Ml51758; Tue, 16 Jul 2002 11:00:22 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15668.13574.480189.404472@grasshopper.cs.duke.edu> Date: Tue, 16 Jul 2002 11:00:22 -0400 (EDT) To: ntai@mac.com Cc: freebsd-stable@freebsd.org Subject: Re: mbuf clusters behavior (NMBCLUSTERS) In-Reply-To: <867kjvoj9f.wl@mac.com> References: <86k7nwwttv.wl@mac.com> <867kjvoj9f.wl@mac.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Naoyuki Tai writes: > > If someone can answer this question, I can probably start troubleshoot > the problem. > > After nfs server uses up the mbuf clusters, how are the mbuf clusters > flushed? An nfs server does not use up the clusters; data is copied from clusters into the buffer cache, then written to disk. > Should I try to change "maxusers 0" to a number like 10? No! > One thing I forgot to mention is that the file system uses soft update. > Would it matter? No. None of this matters. You're getting killed by lots of IP frags because of RH Linux's stupid 16K UDP read/write defualts. As I suggested in my previous message, you should reduce net.inet.ip.maxfragpackets and reduce the read/write size the linux clients are using (change the default in their fstabs). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message