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]

Message-ID: <20111206082247.GA29089@electric-eye.fr.zoreil.com>
Date:	Tue, 6 Dec 2011 09:22:47 +0100
From:	Francois Romieu <romieu@...zoreil.com>
To:	Chris Adams <cmadams@...aay.net>, netdev@...r.kernel.org,
	hayeswang <hayeswang@...ltek.com>
Subject: Re: r8169 performance?

Chris Adams <cmadams@...aay.net> :
> Once upon a time, Francois Romieu <romieu@...zoreil.com> said:
[...]
> > 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).

Ahh, I looked at the patched driver.

It will disappear once http://marc.info/?l=linux-netdev&m=132306718323579
is applied. You may apply http://marc.info/?l=linux-netdev&m=132306715823570
too but I doubt it will make much difference for you.

> 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?

(I understand that the systems (CPU, bus...) are not necessary the same.)

Did you check if Tx checksumming is enabled ?

It could make a noticeable difference.

-- 
Ueimor
--
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