From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Adams Subject: Re: r8169 performance? Date: Mon, 5 Dec 2011 08:54:54 -0600 Message-ID: <20111205145454.GA26078@hiwaay.net> References: <20111204211007.GA32098@hiwaay.net> <20111204234004.GA32515@electric-eye.fr.zoreil.com> <20111205004650.GA5948@hiwaay.net> <20111205064403.GA3426@electric-eye.fr.zoreil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org, hayeswang To: Francois Romieu Return-path: Received: from fly.hiwaay.net ([216.180.54.1]:38938 "EHLO fly.hiwaay.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932281Ab1LEOzA (ORCPT ); Mon, 5 Dec 2011 09:55:00 -0500 Content-Disposition: inline In-Reply-To: <20111205064403.GA3426@electric-eye.fr.zoreil.com> Sender: netdev-owner@vger.kernel.org List-ID: Once upon a time, Francois Romieu said: > Chris Adams : > [...] > > On the "problem" computer (on Fedora 16, kernel 3.1.2): > > > > [ 7.101106] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > > [ 7.102665] r8169 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > > [ 7.107308] r8169 0000:02:00.0: setting latency timer to 64 > > [ 7.107370] r8169 0000:02:00.0: irq 42 for MSI/MSI-X > > [ 7.107703] r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xffffc900112fc000, 00:19:66:f2:dc:0b, XID 081000c0 IRQ 42 > > > > On the "okay" computer (on Fedora 14, kernel 2.6.35.14): > > > > [ 9.053574] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > > [ 9.053594] r8169 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > > [ 9.053689] r8169 0000:06:00.0: setting latency timer to 64 > > [ 9.053740] r8169 0000:06:00.0: irq 47 for MSI/MSI-X > > [ 9.053830] r8169 0000:06:00.0: eth0: RTL8168d/8111d at 0xffffc90012998000, 6c:f0:49:b7:67:91, XID 083000c0 IRQ 47 > > Almost the same: RTL_GIGA_MAC_VER_25 versus RTL_GIGA_MAC_VER_26 (faster). Ahh, my eyes didn't see that one bit difference. > The only difference in the driver is the hw_phy_config part. There's also a difference in the interrupt handling (looks like only in the receive FIFO overflow case). Also, they load different firmware (so I guess my problem could be firmware related, which I guess only RealTek could find/fix). I guess my question is this: is there a chance this can be solved with driver changes, or should I just accept that the on-board NIC has poor performance and install an add-in NIC? -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.