LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 02-23-2004, 07:46 PM   #1
birkinshawc
LQ Newbie
 
Registered: Feb 2004
Posts: 10

Rep: Reputation: 0
Slooooow gigabit on Redhat 9: HELP!!


I have a gigabit NIC (RT 8169) in my Redhat 9 box (distro = Clarkconnect Gateway 2.1) linked up with a crossover cable to a Windoze XP box containing an identical card. The cable run is about 1m and is screened patch.

The XP box is an XP2100 and the linux box a Duron 800. Both have plenty of idle CPU power.

The ping to the XP box is around 0.7 ms from the linux machine so this would indicate a low TCP receive window should be used. I have found, using iperf, that the maximum bandwidth I can obtain is around 270Mbits/sec.


My /etc/sysctl.conf contains the following lines to set TCP parameters:


# increase Linux TCP buffer limits
net.core.rmem_max = 8388608
net.core.wmem_max = 8388608
net.core.rmem_default = 65536
net.core.wmem_default = 65536

# increase Linux autotuning TCP buffer limits
# min, default, and max number of bytes to use
net.ipv4.tcp_rmem = 4096 87380 8388608
net.ipv4.tcp_wmem = 4096 65536 8388608
# number of pages, not bytes
net.ipv4.tcp_mem = 4096 4096 4096


My MTU is set to 1500 on the XP box and linux box. On my XP box the TCP RWIN is set to 65536.

By using the -w flag in iperf I was able to check out different RWIN settings, and found very little difference between settings - below 10k their was a negative effect on throughput, but all other values resulted in 270Mbit/sec. Is this normal?

I have changed network cable, and still cannot get more than 270Mbits/sec transfer from iperf.

If samba was able to use this bandwidth it'd be less than I had expected from gigabit, but still an improvement over 100Mbit. However, samba transfer clock in at around 8MBytes/sec - the same as when I had a 100Mbit link through a cheap hub.
I have recently "upgraded" from Samba 2 to 3 and saw my samba transfer speeds over this link fall from 8MBytes/sec to a pathetic 2MBytes/sec - but that's another story!!

Has anyone any ideas as to why my network performance is so bad? (and if anyone can solve the samba issue I'd be appreciative)

Kind Regards,
Chris

Last edited by birkinshawc; 02-23-2004 at 07:48 PM.
 
Old 02-23-2004, 07:55 PM   #2
snacky
Member
 
Registered: Feb 2004
Distribution: Debian
Posts: 286

Rep: Reputation: 30
I don't want to disappoint you, but 270mb/s sounds fantastic to me. It is unusual to get much better than half the theoretical max even in a 2-node network - for instance, 50mb/s real-world throughput is extremely good for 100mbit ethernet. 270mb/s seems to be in the ballpark of what's good. You may be bumping up against the maximum capability of your medium, but don't expect to do drastically better without spending drastically more money...

As for SMB, what is the CPU usage like? I should add that SMB was never designed with great speed in mind, and I'm wholly unqualified to comment on why 3 does so much worse than 2.
 
Old 02-23-2004, 08:09 PM   #3
birkinshawc
LQ Newbie
 
Registered: Feb 2004
Posts: 10

Original Poster
Rep: Reputation: 0
On the linux box smbd is using 30-40% of CPU when transferring. After an XP reboot I managed to transfer at 8 MB/sec which is little better than what I used to get with my 100Mb LAN.

I just noticed that "ethtool eth2" returns:

Settings for eth2:
No data available

And mii-tool returns:

eth0: autonegotiation failed, link ok
eth1: negotiated 100baseTx-FD, link ok
SIOCGMIIPHY on 'eth2' failed: Operation not supported


How do I fix this?

EDIT: My gigabit card is configured as eth2. ifconfig gives:

eth0 Link encap:Ethernet HWaddr 00:E0:4C:EB:81:FB
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12078226 errors:441 dropped:20 overruns:420 frame:0
TX packets:13033757 errors:0 dropped:0 overruns:0 carrier:0
collisions:39173 txqueuelen:100
RX bytes:458348486 (437.1 Mb) TX bytes:4049385425 (3861.7 Mb)
Interrupt:10 Base address:0x9000

eth1 Link encap:Ethernet HWaddr 00:40:95:10:0F:14
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3679831 errors:0 dropped:0 overruns:0 frame:0
TX packets:6366407 errors:0 dropped:0 overruns:16 carrier:0
collisions:0 txqueuelen:100
RX bytes:3580866650 (3414.9 Mb) TX bytes:3086206436 (2943.2 Mb)
Interrupt:11 Base address:0xb000

eth2 Link encap:Ethernet HWaddr 00:0A:CD:08:7A:EF
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2114500 errors:0 dropped:0 overruns:0 frame:0
TX packets:4302411 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:438199270 (417.8 Mb) TX bytes:0 (0.0 b)
Interrupt:12 Base address:0x1000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:121067 errors:0 dropped:0 overruns:0 frame:0
TX packets:121067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:51154491 (48.7 Mb) TX bytes:51154491 (48.7 Mb)

Last edited by birkinshawc; 02-23-2004 at 08:36 PM.
 
Old 02-23-2004, 08:42 PM   #4
snacky
Member
 
Registered: Feb 2004
Distribution: Debian
Posts: 286

Rep: Reputation: 30
Quote:
On the linux box smbd is using 30-40% of CPU when transferring. After an XP reboot I managed to transfer at 8 MB/sec which is little better than what I used to get with my 100Mb LAN.
This illustrates how complicated the problem is, you have two rather different pieces of software sitting on either end of the cable. Hopefully someone with direct experience of how to best set up both ends will step in.
 
Old 02-23-2004, 08:57 PM   #5
birkinshawc
LQ Newbie
 
Registered: Feb 2004
Posts: 10

Original Poster
Rep: Reputation: 0
Thanks for your help slacky, if anyone else has any ideas about samba or the ethtool results then please step in!!
 
Old 02-26-2004, 04:24 AM   #6
culater
LQ Newbie
 
Registered: Feb 2004
Posts: 1

Rep: Reputation: 0
probably bad driver

It seems that the stock driver on RH9.0 and even the one from realtek website has a few issues. Lockup under nfs and poor performance. There's a patch for the lockup, but still getting reports that performance is equal or worse than a 100MB card.

http://www.spinics.net/lists/kernel/msg239322.html
http://www.spinics.net/lists/kernel/msg245990.html


http://www.ussg.iu.edu/hypermail/lin...12.2/0329.html

http://www.ussg.iu.edu/hypermail/lin...12.1/1769.html

http://www.fr.zoreil.com/linux/kerne....0-test11-bk5/


Sorry, no actual fix for RH9.0 yet.
 
Old 02-27-2004, 01:45 AM   #7
bdp
Member
 
Registered: Apr 2002
Distribution: RH 9
Posts: 230

Rep: Reputation: 30
i use intel pro 1000 gigabit cards w/ crappy crossover cable (old cat5 laid eons ago in bldg) and rh9 btwn athlon XP2000 and P2@350MHZ, which gives ~45 MB/s over the wire and moves files over 20MB/s, limited by the slow HD on the P2 server. for $35 each these are great cards.

sorry, don't know about your cards but gives a benchmark of sorts.
 
Old 03-02-2004, 09:35 AM   #8
birkinshawc
LQ Newbie
 
Registered: Feb 2004
Posts: 10

Original Poster
Rep: Reputation: 0
Thanks for the advice guys, guess I 'll just have to wait until realtek update their drivers.

bdp: what are you samba settings and your TCP receive window settings?
 
Old 03-03-2004, 01:49 AM   #9
bdp
Member
 
Registered: Apr 2002
Distribution: RH 9
Posts: 230

Rep: Reputation: 30
hi birkinshawc,

latency is low (ping times ~0.03ms) so i never tweaked with the default TCP receive window, i'm getting lazy with age...

as for samba settings, i should have specified that i'm using NFS on both ends, finally got rid of windows around here

cheers - bp
 
Old 03-13-2004, 10:31 AM   #10
Merlin-TC
LQ Newbie
 
Registered: May 2003
Location: Germany
Distribution: Gentoo
Posts: 16

Rep: Reputation: 0
I am having the same problems with the card. I am only running it in 100MBit mode but the transfer rates are still pretty low, like 5-6MB per second.
And I also do think that the bad drivers are responsible for this.
I also made some tests with iperf with different machines connected to this one.
With the 2.6 kernel and the drivers that are integrated in it the card is unusable via UDP traffic at all. When you copy from that machine I get around 2MB/s and when I copy something on it I have around 2-6KB/s (yes, I mean kilobyte).

With the 2.4 series and the drivers the performance is like I mentioned above.
If anyone has any more input about this problem I'd be happy to hear about it.

Thanks
 
Old 03-14-2004, 10:32 AM   #11
gafami
LQ Newbie
 
Registered: Jul 2003
Posts: 2

Rep: Reputation: 0
same here with fedora / core 1.... dmesg/ethtool report that my intel 1000 mt pro card got a 1000mbit connection, however whatever I try... i never exceed 8-10 megabytes per second...
 
Old 10-09-2004, 03:53 PM   #12
fortezza
Member
 
Registered: Mar 2003
Location: Colorado
Distribution: Fedora Core 4
Posts: 297

Rep: Reputation: 30
Lightbulb

Same here. though I am getting 8-10MBps over the 3-4MBps rate I had with 100MB connection. I tried tweaking my network settings by performing the following commands on each computer ( with Gigabit NIC )
ifconfig eth0 mtu 9000 ( sets the mtu up to 9000 )
ifconfig eth0 txqueuelen 2000 (ups the transmit queue size to 2000 )

its still really slow. The funny thing is the first time I transferred a file over the gigabit connetion ( before any tweaks ), it went at 40MBps, but I can't repeat that speed.


Anyhow, I noticed that the driver for the NIC I have ( SMC 9452TX ) is labled as 'unsafe' when I look at it with lsmod. So right now I am trying to install the driver from the vendor's site, but their installer complains that my kernel header and kernel versions do not match. I guess finding the source for my kernel ( installed via yum update command ) willfix this, but I am having a heck of a time finding it - 2.6.7-1.456_4.rhfc2.atsmp.

Another clue that the driver is the issue is the neither "ethtools eth0" or "mii-tools eth0" commands can retrieve any info about my network card, which I read is the responsibility of the driver to return this information.



I'll let everyone know how it turns out.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dhcp slooooow matrixon Linux - Wireless Networking 1 04-23-2005 08:42 PM
Problem /w 3com gigabit controler in redhat 9 EMP_JC Linux - Hardware 0 07-19-2004 01:38 AM
Linksys Gigabit 1064 NIC card under Redhat 7.3 brettjbuckley Linux - Hardware 0 06-09-2004 09:23 AM
Server running very Slooooow? ejennings_98 Linux - Newbie 4 02-24-2004 03:44 PM
RedHat Linux 9.0 and 3Com Gigabit LOM 3C940 litan1 Linux - Hardware 7 08-14-2003 09:28 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 05:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration