From owner-freebsd-current@FreeBSD.ORG Wed Jul 22 23:15:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 739F51065674 for ; Wed, 22 Jul 2009 23:15:26 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from mail.chrishedley.com (77-44-98-139.xdsl.murphx.net [77.44.98.139]) by mx1.freebsd.org (Postfix) with ESMTP id 1D21B8FC08 for ; Wed, 22 Jul 2009 23:15:25 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id C276B6D960; Thu, 23 Jul 2009 00:15:23 +0100 (BST) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5UgrgQgYogl1; Thu, 23 Jul 2009 00:15:20 +0100 (BST) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 4A52C6D945; Thu, 23 Jul 2009 00:15:20 +0100 (BST) Date: Thu, 23 Jul 2009 00:15:20 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: Matthew Dillon In-Reply-To: <200907222307.n6MN7YhU012788@apollo.backplane.com> Message-ID: References: <200907222307.n6MN7YhU012788@apollo.backplane.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: Linux NFS ate my bge X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2009 23:15:26 -0000 On Wed, 22 Jul 2009, Matthew Dillon wrote: > If you are using a NFS UDP mount, try using a NFS TCP mount instead. > This could very well instantly fix your issues even if it does not > solve the underlying bugs. > ... > Use of a TCP mount instead of a UDP mount solves the sockbuf and > IP fragmentation issues. The TCP connection will not use fragmented IP > packets, will not blow away the server's receive-side sockbuf, and > does a much better job dealing with any packet loss, to boot. "But I'm already using TCP!" I was about to say - actually turns out I'm not, and I have to wonder if my bright idea to change to UDP (probably for performance reasons, though I don't think it made any difference) coincides with the problems I was seeing. I'll give it a try and see how I get on. I think I'll still follow Daniel's kind suggestion for a replacement interface card, but this may well make things a bit less painful in the meantime. I'll resume my network-intensive KDE build tomorrow and post my findings (or, hopefully, lack thereof as far as outages are concerned!) Chris.