Date: Sat, 17 Feb 2007 07:27:16 +1100 From: "Dimuthu Parussalla" <dparussalla@baysidegrp.com.au> To: "'Sten Daniel Soersdal'" <sten.daniel.sorsdal@gmail.com> Cc: 'Vinny Abello' <vinny@tellurian.com>, freebsd-stable@freebsd.org Subject: RE: Slow network performance Message-ID: <002101c75208$da05aed0$d801a8c0@dimuthu> In-Reply-To: <45D5CE9C.8020907@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sten, I have ruled out the faulty cable. Also no errors reporting on the managed switch. Doing a test with a reduced parameters to 32k. -----Original Message----- From: Sten Daniel Soersdal [mailto:sten.daniel.sorsdal@gmail.com] Sent: Saturday, 17 February 2007 2:33 AM To: Dimuthu Parussalla BWEADM non-std-pwd Cc: Vinny Abello; freebsd-stable@freebsd.org Subject: Re: Slow network performance Dimuthu Parussalla BWEADM non-std-pwd wrote: > This is exactly what I did. > Managed Switch A (2950G) > 1) both switch and bge/em card set for auto negeotiation > 2) Both switch and bge/em set for 1000mb full-duplex. > > Managed Switch B (Netgeat GSM7224) > 1) both switch and bge/em card set for auto negeotiation > 2) Both switch and bge/em set for 1000mb full-duplex. > > I am seriously running out of options. > Thanks What have you done to rule out if it's a faulty cable or noise on the cable? What kind of cable is it? net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 Are you sure these two should be set to the millions? Try reducing them to ~32k or so. -- Sten Daniel Soersdal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002101c75208$da05aed0$d801a8c0>