Re: Realtek RTL8111B serious performance issues

[john@BlueSkyTours.com]

On Thu, 19 Jul 2007, Bill Fink wrote:

> Hi John,
>
> On Wed, 18 Jul 2007, john@BlueSkyTours.com wrote:
>
>> On Wed, 18 Jul 2007, Francois Romieu wrote:
>>
>>> john@BlueSkyTours.com <john@BlueSkyTours.com> :
>>> [...]
>>>> 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:
>>> http://www.fr.zoreil.com/people/francois/misc/20070628-2.6.22-rc6-r8169-test.patch
>>
>> Unfortunately, the 20070628 patch did not make any difference.
>>
>>
>>> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc6/r8169-20070628/
>>
>>
>> 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 192.168.26.150: 56 data bytes
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=0. time=0.287 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=1. time=0.279 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=2. time=0.196 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=3. time=0.201 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=4. time=0.159 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): icmp_seq=5. time=0.148 ms
>> 64 bytes from dyn26-1.blueskytours.com (192.168.26.150): 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.

John

P.S. I did send the pcap files to Francois Romieu, but I did not CC the list
because they were large.