[haiku-bugs] [Haiku] #8454: Very low network performance with a Marvell Yukon card.
- From: "bga" <trac@xxxxxxxxxxxx>
- Date: Sat, 07 Apr 2012 15:38:02 -0000
#8454: Very low network performance with a Marvell Yukon card.
-------------------------------------------+------------------------------
Reporter: bga | Owner: nobody
Type: bug | Status: new
Priority: high | Milestone: R1
Component: Drivers/Network/marvell_yukon | Version: R1/Development
Keywords: | Blocked By:
Blocking: | Has a Patch: 0
Platform: All |
-------------------------------------------+------------------------------
It has been a long time since I last used Haiku but I recently started
using it again. I noticed there has been a huge network performance
regression (more likelly, with my specific card as someone else would
have noticed it if the problem was more general).
Here is my card:
{{{
/dev/net/marvell_yukon/0
Hardware type: Ethernet, Address: 00:1e:8c:3a:65:24
Media type: 1 GBit, 1000BASE-T
inet addr: 192.168.0.11, Bcast: 192.168.0.255, Mask: 255.255.255.0
inet6 addr: fe80::21e:8cff:fe3a:6524, Bcast:
ffff:ffff:ffff:ffff::, Prefix Length: 64
MTU: 1500, Metric: 0, up broadcast link auto-configured
Receive: 5880 packets, 0 errors, 4661150 bytes, 0 mcasts, 0 dropped
Transmit: 2737 packets, 0 errors, 253011 bytes, 0 mcasts, 0 dropped
Collisions: 0
}}}
As you can see it is connected to a Gigabit ethernet network and the
speed is not getting even close to that. And when I say not even close
I do not say I am getting 10 Mbits or something. I am getting amazing
425 Kbits! or 52 kb/s in the local network. The same machine also runs
Linux and when booted to it, I get around 40 mb/s of transfer speed.
Also, ping times are surreal:
{{{
[/boot/home]> ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=333.856 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=334.960 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=336.313 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=337.703 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=339.046 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=340.501 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=341.911 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=343.321 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=344.734 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=346.066 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=347.479 ms
--- 192.168.0.1 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 333.856/340.535/347.479/4846.743 ms
}}}
On Linux on the same machine, the same ping results in sub-ms reply time,
so this is aroung 500 times slower!
Also notice this card use the FreeBSD compatibility layer. It is possible
that the problem is there.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8454>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
