From owner-freebsd-stable Sun Apr 1 17:37:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id AD7D837B71F for ; Sun, 1 Apr 2001 17:37:39 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 75998 invoked by uid 1000); 2 Apr 2001 00:38:00 -0000 Date: Mon, 2 Apr 2001 02:38:00 +0200 From: "Karsten W. Rohrbach" To: Mike Smith Cc: "David W. Chapman Jr." , "Jason T. Luttgens" , freebsd-stable@freebsd.org Subject: Re: Network performance question Message-ID: <20010402023800.B75063@mail.webmonster.de> References: <009901c0bad3$3e708080$931576d8@inethouston.net> <200104011725.f31HPSC00996@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104011725.f31HPSC00996@mass.dis.org>; from msmith@freebsd.org on Sun, Apr 01, 2001 at 10:25:28AM -0700 X-Arbitrary-Number-Of-The-Day: 42 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith(msmith@freebsd.org)@2001.04.01 10:25:28 +0000: > > > FreeBSD kinda disappointed me. It gets ~1000 interface errors on about > > > 514000 packets. I switched the 3COM card out for a NetGear FA311 (sis > > > driver). After receiving ~310000 packets, the network goes down (can't > > > ping/telnet anywhere). At that point I have to ifconfig down and up the > > > interface to get it back. > > You're disappointed in *FreeBSD* because of this? These are *hardware* > failures you're describing here... > mike, driver stuff can be implemented in not just one way or style of code as we all know. the freebsd approach is to have readable code, no awkward hacks (well, errrhm, almost ;) and a structure that meets the specifications of the hardware and, hopefully, is extendible for newer hw versions. the linux approach is to have a flying penguin touching the ground with the tip of his left foot, trying not to crash into the next obstacle - and so is the source. the linux community tends to fix driver problems on certain hardware with evil hacks and, hell, at least it _seems_ to work ;-) for my production systems i prefer the first option, anyway. for the hardware issues in the original mail: - i do not use any 3com equipment anymore since 3com is evil - i like intel 82559 or dec 21141 chipsets, i got some boxes running with smc etherpower ii, too - for a packet capture system analyzing netbios traffic on a switched ethernet via replicating a whole 100mbps switch backplane onto one 1000SX interface i used tigon ii cards (netgear ga620) - the only os that could handle the traffic with bpf/pcap and to the log weeding and storage on one p-iii 500 box was freebsd - one has to know the doodads of kernel configuration. i think, that especially maxusers should be higher by default in the GENERIC kernel, not to talk about options NMBCLUSTERS that should be 8192 minimum - sure, fact is that one needs to configure a kernel for specific tasks like capturing high volume traffic from a network, but that's a typical RTFM issue - anyway the kernel configuration options could be documented much much better btw, i just tried the serverworks based asus board you recommended me at bsdcon2k - runs like a charm ;-) thanks! /k -- > Friends don't let friends use sendmail. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message