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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 19 Jul 2007 10:00:11 -0600 (MDT)
To:	Bill Fink <>
Subject: Re: Realtek RTL8111B serious performance issues

On Thu, 19 Jul 2007, Bill Fink wrote:

> Hi John,
> On Wed, 18 Jul 2007, wrote:
>> On Wed, 18 Jul 2007, Francois Romieu wrote:
>>> <> :
>>> [...]
>>>> Anyone have any suggestions for solving this problem?
>>> Try 2.6.23-rc1 when it is published or apply against 2.6.22 one of:
>> Unfortunately, the 20070628 patch did not make any difference.
>> I tried various patches from that directory (aren't most or all of them
>> included in the 20070628 patch?), but none of them helped either.
>> This problem could be very difficult to track down.  Like I said, it
>> definately effects emacs and firefox being "drawn" on a remote computer.
>> Ping times, however, are not that bad:
>> PING 56 data bytes
>> 64 bytes from ( icmp_seq=0. time=0.287 ms
>> 64 bytes from ( icmp_seq=1. time=0.279 ms
>> 64 bytes from ( icmp_seq=2. time=0.196 ms
>> 64 bytes from ( icmp_seq=3. time=0.201 ms
>> 64 bytes from ( icmp_seq=4. time=0.159 ms
>> 64 bytes from ( icmp_seq=5. time=0.148 ms
>> 64 bytes from ( icmp_seq=6. time=0.150 ms
>> Also, wget gets good throughput when retrieving files.
>> It just seems to be X traffic which is extremely slow.  Using the old
>> Linksys 10/100 PCI NIC, emacs comes up virtually instantaneously.  Using the
>> integrated Realtek 8111B, emacs takes 10 seconds to draw.
>> Thank you very much for trying to help.
> Any chance that the Realtek 8111B is sharing interrupts with another
> device ("cat /proc/interrupts")?  Perhaps it is, and the Linksys isn't,
> which could explain the difference in behavior.  Just something simple
> to check and either rule in or out.

Yes it was, however "fixing" that did not solve the problem.

Thanks for the thought.


P.S. I did send the pcap files to Francois Romieu, but I did not CC the list
because they were large.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists