2 ms·
I've had good experience with Realtek NICs too, not 2.5g yet but their 10/100/1000 models. I suspect that's because they use a far simpler design with not much
by userbinator 4y ago
I've had good experience with Realtek NICs too, not 2.5g yet but their 10/100/1000 models. I suspect that's because they use a far simpler design with not much in the way of fancy features[1]. They also tend to benchmark slower with higher CPU usage, but I'll take slightly slower but stable over fast but intermittent connectivity.
[1] Ironically, in this case the Intel has to have a fancy feature, intended for increasing performance, disabled in order to increase performance.
- toast0 4y agoI've heard good things about Realtek's 2.5G nics, and bad things about Intel's; I've seen speculation that underlying cause is cross compatability between the two 2.5g specs that were merged into the standard and that most 2.5g switches use chips from companies that were behind the spec Intel was not behind. For 1G realteks, I've had ok luck with them, but I do see some issues. I recall having some problem with them while running the Linux tree drivers, but I've since switched to all FreeBSD. With my current realtek NICs and FreeBSD 13.1, I have the choice of the kernel driver where sometimes the NIC will stop processing packets, and the NIC acknowledges reset, but doesn't actually immediately reset and sometimes processes old packets after resetting, resulting in wild writes and bad behavior. There's a vendor driver, which doesn't seem to get into that bad state, but it does enable ethernet PAUSE frames which are an abomination. The vendor driver is full of undocumented magic values and there's no public documentation on the NICs at all, so figuring out what to frob to make the NIC not get stuck, but not send out PAUSE frames would be an exercise in frustration, that I'm not willing to do. Either way, the interrupt design is deficient: there's a shared interrupt for rx, tx and administration, and the status register doesn't really work right either --- it's possible for the host and device to disagree about what irqs were acknowleged and then things will get stuck (that doesn't seem to be the FreeBSD driver issue though; you can work around the stuck status communications by just assuming something probably happened aftet a few seconds, or checking for descriptor progess on rx and tx on any interrupt, etc). Having only a single interrupt means you can't meaningfully process incomming packets and finished outgoing descriptors in parallel which makes it hard to get full throughput in both directions simultaneously. Anyway --- if they work for you, great. I'm going to avoid them where practical, and be careful with them elsewhere.
- 3np 4y agoSame. From lore and experience, Intel is more stable than Realtek for 1G on Linux.
- bayindirh 4y agoIntel managed to break some of their older consumer 1G NICs under Linux pretty reliably while adding support for newer NICs, and failed to fix them for a very long time. At the end, Debian reverted Intel's patches and shipped a modified version which probably didn't enable some features on the newer NICs, but didn't break the older ones in the process. It's ironic that the underdog Realtek has much more reliable cards which doesn't shudder under constant load and/or very long uptime scenarios. Realtek won't cut in server scenarios, but Intel's and Broadcom's server class NICs are completely different beasts when compared to Intel's consumer NICs, too. Wish they had given some more attention to them while developing their drivers.
- userbinator 4y agoand there's no public documentation on the NICs at all There is plenty if you search around, and they're one of the recommended NICs if you want to write an OS/driver because of that; they also show up in virtual form in various VM hosting software due to their simplicity: https://wiki.osdev.org/RTL8139 https://wiki.osdev.org/RTL8139 https://wiki.osdev.org/RTL8169 https://wiki.osdev.org/RTL8169 https://www.iitg.ac.in/asahu/cs421/RealTek.pdf https://www.iitg.ac.in/asahu/cs421/RealTek.pdf
- toast0 4y agoOk yes. I've done that actually. Pretty sure I used that pdf (or similar, although I think the one I used was marked confidential). But a pdf from 2002 tha is hosted from a university, not the vendor, isn't really up to the standard of public documentation. It wouldn't be so bad if their vendor drivers had comments or even sensible names for values when they frob the hardware, but it's just hex values with no explanations. It's an OK NIC to work with hobby wise, although I quickly ran into issues with the status register, and I can only hope one day I'll get enough throughput to overwelm the nic. And then I'll move to an Intel nic of which I have several.
- cduzz 4y agoThis is the classic Sutherland "wheel of reincarnation" cycle -- a function (commonly graphics acceleration or network connectivity) will be provided by the CPU, which is found to be a bottleneck so the function is offloaded to a dedicated device, which then becomes a bottleneck as the CPU receives more dedicated focus on performance improvement than some bespoke, single-purpose offload engine.