From owner-freebsd-hackers Thu Apr 4 7:31:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6D0F837B41E for ; Thu, 4 Apr 2002 07:31:49 -0800 (PST) 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 KAA20561; Thu, 4 Apr 2002 10:31:36 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g34FV6i98517; Thu, 4 Apr 2002 10:31:06 -0500 (EST) (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: <15532.29114.310072.957330@grasshopper.cs.duke.edu> Date: Thu, 4 Apr 2002 10:31:06 -0500 (EST) To: Will Froning Cc: hackers@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode In-Reply-To: <20020403181854.I42720-100000@angui.sh> References: <20020403181854.I42720-100000@angui.sh> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Will Froning writes: > I have a 4.5-RELEASE-p2 box that is my Firewall/NAT/NFS server. As a > NFS client I have a RH7.2 linux box. When I do massive NFS writes to > my FBSD (from RH7.2 box), I get a panic. I've attached the info I got > from my debug kernel. > While the fix being discussed by Peter & others will prevent panics, the linux box will still run your server out of mbufs clusters. This is happening because the linux box is using a 16K write size over UDP by default. This is a stupid default. If there is any lossage between the hosts (eg, any packets get dropped), more and more packets will end up on the reassembly queues. Eventually, all your cluster mbufs will be there. I suggest changing the mount options on the linux box to use 8k reads and writes, or use TCP. Another problem I've see w/Linux NFS clients is that recent linux NFS clients seem to spew ACCESS requests like there's no tomorrow & beats the snot out of my NFS server. When building large software pacakges via "make -j4" over NFSv3 (100Mb ethernet) on a dual PIII 1GHz system, a FreeBSD 4.5 host issues 400-500 ACCESS calls/sec. A Linux 2.4.18 host spews 12,000 - 14,000 ACCESS calls/sec, or roughly 30 times as many. Needless to say, the build finishes a whole lot quicker on FreeBSD. Does anybody know what I can do to make the linux client cache ACCESS info? Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message