From owner-freebsd-hackers Thu Jun 8 22:20:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id B0D6A37C1B0 for ; Thu, 8 Jun 2000 22:20:46 -0700 (PDT) (envelope-from jhix@mindspring.com) Received: from mindspring.com (user-33qtgqb.dialup.mindspring.com [199.174.195.75]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id BAA18226; Fri, 9 Jun 2000 01:20:39 -0400 (EDT) Message-ID: <39407EC9.D2204561@mindspring.com> Date: Thu, 08 Jun 2000 22:21:13 -0700 From: W Gerald Hicks X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: hackers@FreeBSD.ORG Subject: Re: if_dc in v4.0 - Forcing store and forward? References: <393F33A1.2AE75730@mindspring.com> <37865.960493076@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > > > I suspect a generic chipset fault, or some design quirk that we are not > > > working around. Note that the windoze drivers for these devices put them > > > permanently in store-and-forward mode. if_de has the exact same problem on > > > all of the systems above. > ... > > Store and forward mode introduces a horrible performance hit... Artesyn > > wouldn't show us the source to their workaround :-( > > It should be noted that I was able to saturate a 100 Mbps Ethernet with > FreeBSD 2.2 and a 21140 based card, using around 56% of the CPU of a > PPro-200. This was done almost exactly three years ago, using the (then) > standard if_de driver. I have no idea whether the card was operating in > store-and-forward mode or not - but the performance was perfectly fine. I can guarantee that it was not running in store and forward mode if you were exceeding 30 Mbit throughput. Was this a 21140, 21140A or other stepping? These variations varied pretty wildly in their behavior (and I suspect in their actual implementation as well). Cheers, J. Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message