From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 21 20:23:14 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 688841065688 for ; Sun, 21 Jun 2009 20:23:14 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6C23B8FC2A for ; Sun, 21 Jun 2009 20:23:12 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n5LKMHGE077284; Sun, 21 Jun 2009 22:22:17 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n5LKMExr077281; Sun, 21 Jun 2009 22:22:16 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 21 Jun 2009 22:22:12 +0200 (CEST) From: Wojciech Puchar To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86eitdy4hl.fsf@ds4.des.no> Message-ID: References: <86eitdy4hl.fsf@ds4.des.no> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: is RTL8139 THAT bad? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2009 20:23:14 -0000 > Wojciech Puchar writes: >> Why it's THAT bad? > > http://svn.freebsd.org/base/head/sys/pci/if_rl.c > > Scroll down past the copyright, license and attribution. Read the > 38-line comment that explains just how crappy this chip really is. Well - really "low end". But - this computer can do memcpy at 80MB/s, so at 3.5MB/s it should be 5% CPU for memcpy, and one interrupt per one packet (2500 packets/s). Is something more that make it consume >50% CPU?