From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:37:17 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 149F916A420; Thu, 24 Nov 2005 00:37:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43850B4E.6050301@freebsd.org> Date: Thu, 24 Nov 2005 08:37:34 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200511231406.06282.jhb@freebsd.org> In-Reply-To: <200511231406.06282.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: nve locking fixes round 2 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: Thu, 24 Nov 2005 00:37:17 -0000 John Baldwin wrote: >Ok, now that the first set of locking overhaul is in the tree, can folks with >working nve(4) adapters test the patch referenced below and make sure there >are no regressions. Having the IFF_UP fiddling turned off may or may not >help folks getting the TX timeouts as well, btw, so if people are feeling >brave they can try this patch as well. Note it is only applicable to recent >current. > >http://www.FreeBSD.org/~jhb/patches/nve_locking.patch > > > Make no difference on my AMD64 machine,dmesg: http://people.freebsd.org/~davidxu/epox9nda3j.txt