From owner-freebsd-stable Wed Sep 15 7:19:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by hub.freebsd.org (Postfix) with SMTP id 557321526C for ; Wed, 15 Sep 1999 07:19:31 -0700 (PDT) (envelope-from ira@MIT.EDU) Received: from ALL-NIGHT-TOOL.MIT.EDU by MIT.EDU with SMTP id AA25965; Wed, 15 Sep 99 10:19:30 EDT Received: (from ira@localhost) by all-night-tool.mit.edu (8.9.3) id KAA12791; Wed, 15 Sep 1999 10:19:25 -0400 (EDT) Message-Id: <199909151419.KAA12791@all-night-tool.mit.edu> To: freebsd-stable@freebsd.org Subject: Re: 3.3-RC and 3com 509 Driver Date: Wed, 15 Sep 1999 10:19:25 -0400 From: Ira L Cooper Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Sep 14, 1999 at 10:00:09AM -0700, Mike Smith wrote: > > The NIC:driver combination is sometimes buggy. We don't really > > understand why these work well for some people and terribly for others. > > As an example of this, I have three machines with 3c509s in them, which > work fine, and transfer data at the sort of rate you would expect. > > I also have a notebook (Toshiba Portege 3020CT - couldn't get a > Libretto) with a 3CCE589E card. This works OK for interactive use, FTP, > etc. Anything involving bigger transfers often behaves dreadfully. > Every now and again I tinker, trying to get a clue as to the cause. > Below are the elderly remains of one experiment, showing how tar across > the network runs at very variable speeds, depending on the block > size. The file being dumped is 1.3MB in size. Most of the time I just > grit my teeth, and go away while the notebook is being dumped. Can you FTP/SCP large files? I don't understand your test enviornment well enough to duplicate it here. -Ira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message