Date: Tue, 31 May 2005 00:06:13 +0200 From: Sebastian Ahndorf <webmaster@it-is-warlock.de> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: Poor network performance: a lot of timeouts Message-ID: <429B8E55.6090104@it-is-warlock.de> In-Reply-To: <00de01c5655f$08a4e550$b3db87d4@multiplay.co.uk> References: <20050529221024.4fu2p4yjusk04k0g@mail.banot.net> <20050529212705.GA64753@xor.obsecurity.org> <1117447400.5384.4.camel@localhost.localdomain> <20050530104928.GB79877@sr.se> <1117465224.9934.7.camel@localhost.localdomain> <429B44BD.7070806@pp.nic.fi><20050530191843.GA82875@xor.obsecurity.org> <429B7DF6.8040704@it-is-warlock.de> <00de01c5655f$08a4e550$b3db87d4@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Steven Hartland wrote: > > Quite a few 100tx nic / switch combinations misbehave when both > sides are not set to the same be that 100fdx or auto sense. I've actually > never seen a problem with 100tx autoneg as long as both ends had > it selected and there wasn't a cable problem. > I was talking about cheap switches (and that's pretty the same with adsl-routers). There is usually no way to configure (at the switch) which speed/duplex should be used and if you set your nic to a specific mode, the switch doesn't mention this. So it keeps on sending it's autosensepakets and waits for response. It get's timeouts and thats what pulls down the networkperformance. So you have to set your nic to autosense and you'll get a better performance, cause the nic responces to autosense. > Steve Good night, Sebastian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?429B8E55.6090104>