netdev - Re: r8169 performance?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 5 Dec 2011 08:54:54 -0600
From:	Chris Adams <cmadams@...aay.net>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org, hayeswang <hayeswang@...ltek.com>
Subject: Re: r8169 performance?

Once upon a time, Francois Romieu <romieu@...zoreil.com> said:
> Chris Adams <cmadams@...aay.net> :
> [...]
> > 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 <cmadams@...aay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html