Date: Sun, 22 Dec 2002 15:12:59 -0500 From: "matthew c. mead" <mmead@goof.com> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-net@freebsd.org, dillon@freebsd.org Subject: Re: TCP interactions (was: Re: Linux and FreeBSD poor network performance) Message-ID: <20021222151259.A21189@goof.com> In-Reply-To: <Pine.NEB.3.96L.1021222105809.91887B-100000@fledge.watson.org>; from rwatson@freebsd.org on Sun, Dec 22, 2002 at 10:59:52AM -0500 References: <20021221165745.A67089@goof.com> <Pine.NEB.3.96L.1021222105809.91887B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 22, 2002 at 10:59:52AM -0500, Robert Watson wrote: > On Sat, 21 Dec 2002, matthew c. mead wrote: > > 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. > And you've done tests in both directions, or just in one? Both. > Could you try using a non-TCP performance measurement tool of some sort? > I.e., some sort of UDP throughput test. Because of your comment about the > two boxes talking to windows fine, it sounds likely to be a TCP > interaction, but it would be useful to check and see. I didn't get around to it before I started looking at hardware/driver. I dropped a 3c905 into the Linux box and things improved. I grabbed a new ethernet card elsewhere today and it works just fine. > I've CC'd Matt Dillon because he's fixed a number of subtle TCP bugs of > this sort in the past and can probably provide some debugging guidance. I think it's the Linux driver. Sorry for the false alert. This would be a fun one to figure out if it were tcp stack interactions. :( -matt -- 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?20021222151259.A21189>