From owner-freebsd-current@FreeBSD.ORG Mon Apr 2 01:02:43 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8695916A401 for ; Mon, 2 Apr 2007 01:02:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id 3A24F13C458 for ; Mon, 2 Apr 2007 01:02:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id r28so828804nza for ; Sun, 01 Apr 2007 18:02:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=qe0/GHS7gUss8kr7n2VzJdH/xEFUKmn6ZJ669+1wjj2e+XGGqcyWbIp8m2KS/XmfLARfg8xpHp1Vf4YUVsJ2UKmoBnd2lHY4mN/kwbyOqRcCJ6B0HlZfn0rZ7hEgZVdl4TPWZgpt6q+Y/YVrQ8q/NgnWukmqWdJbSPwmrbZIasI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=I4QeE7HffNLnOuDNMX92p9vQAdjZ3hLiEo9COwtXy6diaVghnLsXv/EU7YvkbkEqSrmHC+ptIAyfSPW9j9zJeMZmwrLQiTGvgir879qtehJN6sybcsQMH7yuKZ6Kv5Nows8xOnekidPqE4vAo+Q5gRb+eD8rEkzN5Nx3F1lSpdM= Received: by 10.65.236.14 with SMTP id n14mr8773038qbr.1175475762468; Sun, 01 Apr 2007 18:02:42 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 38sm21451725nza.2007.04.01.18.02.39; Sun, 01 Apr 2007 18:02:41 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l3212VMh001783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Apr 2007 10:02:31 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l3212ULU001782; Mon, 2 Apr 2007 10:02:30 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 2 Apr 2007 10:02:30 +0900 From: Pyun YongHyeon To: Rainer Hurling Message-ID: <20070402010230.GA1323@cdnetworks.co.kr> References: <20070311050627.GC79728@cdnetworks.co.kr> <45F3B94B.3030104@gwdg.de> <20070312045116.GA83433@cdnetworks.co.kr> <45F5C914.3000805@gwdg.de> <20070313004601.GA87608@cdnetworks.co.kr> <20070313005845.GB87608@cdnetworks.co.kr> <45F636B5.9060608@gwdg.de> <20070313070153.GD87608@cdnetworks.co.kr> <20070331003031.GB68853@cdnetworks.co.kr> <460E77BE.9090503@gwdg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <460E77BE.9090503@gwdg.de> User-Agent: Mutt/1.4.2.1i Cc: darren780@yahoo.com, freebsd-current@freebsd.org, Shigeaki Tagashira Subject: Re: yongari nfe problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2007 01:02:43 -0000 On Sat, Mar 31, 2007 at 05:01:18PM +0200, Rainer Hurling wrote: > Thank you Pyun YongHyeon for the newest patch. I am running it with > if_nfe.c and if_nfereg.h from 03/21/2007 and if_nfevar.h from 03/19/2007 > on FreeBSD 7.0-CURRENT (i386) from today. > > boot -v gives me: > nfe0: port 0xb000-0xb007 mem > xfbef3000-0xfbef3fff,0xfbefa800-0xfbefa8ff,0 > xfbefa400-0xfbefa40f irq 22 at device 8.0 on pci0 > nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfbef3000 > miibus0: on nfe0 > ciphy0: PHY 1 on miibus0 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > nfe0: bpf attached > nfe0: Ethernet address: 00:16:17:95:d9:7c > nfe0: [MPSAFE] > nfe0: [FILTER] > > > Now there are no more warning from miibus0 :-) > Thanks for testing. > Unfortunately at bigger network transfers I still observe the previously > described watchdog timeouts: > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > ... > > During these timeouts I am not able to use my network ;-( > > I would be happy if I could help solving this problem. Let me know if I > can test anything. > Does nfe(4) use shared interrupt with other devices? (Check 'vmstat -i' output.) Since the watchdog timeout error indicates you've had missing Tx completion interrupts I guess you've lost Tx completion interrupts under high systems loads. One of major changes in new nfe(4) was switching to so-called adaptive polling and it is known to give better performance. However it can loose interrupts under high system loads (e.g. buildworld) and I guess there are two ways to fix the issue. 1. Add MSI/MSI-X support. I think this is the cleanest solution to the issue. But old hardwares which has no MSI/MSI-X support and buggy PCI bridges may have issues dealing with MSI/MSI-X. In addition, there is no public documentation available for NVIDIA NICs and lack of MSI/MSI-X capable hardwares make me hard to add MSI/MSI-X support. AFAIK, Shigeaki Tagashira is working on supporting MSI/MSI-X.(CCed) 2. polling(4) Because polling(4) does not rely on timed-delivery of Tx interrupts it would help in your case. -- Regards, Pyun YongHyeon