Date: Sat, 21 Dec 2002 17:29:10 -0500 From: "matthew c. mead" <mmead@goof.com> To: Steve Baxter <steve@pipenetworks.com> Cc: freebsd-net@freebsd.org Subject: Re: Linux and FreeBSD poor network performance Message-ID: <20021221172910.A67763@goof.com> In-Reply-To: <Pine.LNX.4.33.0212220814310.12158-100000@internal.pipenetworks.com>; from steve@pipenetworks.com on Sun, Dec 22, 2002 at 08:16:28AM %2B1000 References: <20021221165745.A67089@goof.com> <Pine.LNX.4.33.0212220814310.12158-100000@internal.pipenetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 22, 2002 at 08:16:28AM +1000, Steve Baxter wrote:
> Check out the duplex setting on the ethernet ports. Use
> 'ifconfig' and 'netstat -I dev -w 1' on FreeBSD
ifconfig fxp0:
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.99 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::2d0:b7ff:fe9e:2bbe%fxp0 prefixlen 64 scopeid 0x1
ether 00:d0:b7:9e:2b:be
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
The switch's light for full duplex on this port is ON.
The netstat lists no errors or collisions.
> 'ifconfig', 'mii-tool' and 'cat /proc/net/dev' on Linux
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:07:95:35:DD:77
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:60487 errors:0 dropped:0 overruns:0 frame:0
TX packets:93881 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:19959655 (19.0 Mb) TX bytes:78760612 (75.1 Mb)
Interrupt:5 Base address:0xd400
mii-tool:
eth0: negotiated 100baseTx-FD, link ok
The switch's light for full duplex on this port is ON.
cat /proc/net/dev:
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 1000 20 0 0 0 0 0 0 1000 20 0 0 0 0 0 0
eth0:19971723 60609 0 0 0 0 0 0 78770385 93940 0 0 0 0 0 0
> Any sort of errors may lead to this sort of behaviour. You need to match
> the hosts to the switch port they are connected to.
Thanks for the suggestions. I think the cards/ports are
negotiating with each other properly.
I've tried disabling the FreeBSD box's delay_ack but it makes no
difference.
Any other ideas? Thanks again...
-matt
>
> SB
>
>
> > I have a Linux box and FreeBSD box sitting on a 100Mbit ethernet
> > segment that cannot seem to talk to one another faster than
> > 150K/s. I've been using scp, ftp, http, to test this.
> >
> > A Windows box on the same segment can send/receive at 6MB/s with
> > either box, but for some reason the FreeBSD box and Linux box
> > are having some weird interaction. My guess is I need to tune
> > one or the other's tcp stack. Any hints? Anyone seen this?
> >
> > FreeBSD box is FreeBSD 4.7-RELEASE-p2. Linux box is Gentoo Linux
> > 1.4rc1 with kernel 2.4.19-gentoo-r10. Windows box is Windows
> > 2000 sp3.
> >
> > Thanks in advance for any help... I'm out of ideas.
> >
> >
> > -matt
> >
> >
>
> --
> Stephen Baxter
> Director - PIPE Networks
> phone : 07 3220 1100/ 0417 818 695
> fax : 07 3220 1800
>
>
> ______________________________________
> PIPE Networks/IX Services Australia disclaimer
>
> The above email should be read in conjunction with our standard
> disclaimer/terms which can be found at :
>
> http://www.pipenetworks.com/docs/disclaimer.htm
>
--
matthew c. mead
http://www.goof.com/~mmead/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021221172910.A67763>