From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 22 00:22:51 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 B6D0C1065670 for ; Mon, 22 Jun 2009 00:22:51 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by mx1.freebsd.org (Postfix) with ESMTP id 9574B8FC13 for ; Mon, 22 Jun 2009 00:22:51 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from verizon.net ([98.109.134.167]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KLM00CJC3LFEE71@vms173007.mailsrvcs.net> for freebsd-hackers@freebsd.org; Sun, 21 Jun 2009 18:22:30 -0500 (CDT) Sender: root Message-id: <4A3EC37B.F589EA09@verizon.net> Date: Sun, 21 Jun 2009 19:34:19 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) X-Accept-Language: en, ru MIME-version: 1.0 To: Wojciech Puchar References: <86eitdy4hl.fsf@ds4.des.no> Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 22 Jun 2009 02:16:59 +0000 Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , 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: Mon, 22 Jun 2009 00:22:52 -0000 Wojciech Puchar wrote: > > > 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? Accessing the on-card memory through PCI is guaranteed to be slower than the main memory, and depending on the particular card it may be much slower. -SB