From owner-freebsd-hardware@FreeBSD.ORG Tue May 6 10:25:26 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60C737B404 for ; Tue, 6 May 2003 10:25:26 -0700 (PDT) Received: from arthur.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id D198543F85 for ; Tue, 6 May 2003 10:25:25 -0700 (PDT) (envelope-from simon@arthur.nitro.dk) Received: by arthur.nitro.dk (Postfix, from userid 1000) id 5387410BF81; Tue, 6 May 2003 19:25:24 +0200 (CEST) Date: Tue, 6 May 2003 19:25:24 +0200 From: "Simon L. Nielsen" To: "Jin Guojun [NCS]" Message-ID: <20030506172523.GE428@nitro.dk> References: <3EB7EBB6.3038C32E@lbl.gov> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa" Content-Disposition: inline In-Reply-To: <3EB7EBB6.3038C32E@lbl.gov> User-Agent: Mutt/1.5.4i cc: joe mcguckin cc: hardware@freebsd.org Subject: Re: Intel GigE and copper PHY supported? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 17:25:27 -0000 --5I6of5zJg18YgZEa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003.05.06 10:07:03 -0700, Jin Guojun [NCS] wrote: > joe mcguckin wrote: >=20 > > I'd like to use the TYAN Trinity GC-SL motherboard with on-board GigE > > (copper). Does anyone know if this is supported? Has anyone used this b= oard > > with 4.X? > > > > Thanks, >=20 > Do not have direct use of this motherboard. We have some similar M/Bs > from SuperMicro (same chipset and same GigE NICs). >=20 > General M/B performance is good. The GigE is not too pleasure. > The Incoming TCP is about 350 Mb/s, and out going TCP is only 270, > which is limited by interrupt (98% CPU -- 2.8 GHz -- used for interrupt). > Either the driver or the Intel NIC is not functioning properly, but we do= not > have time to investigate. If this the chips a using the em(4) driver you can try turning on interrupt coalation (or whatever Intel calls it). It can (AFAIR) only be done by modifying sys/dev/em/if_em.h. Just note the warning about why it was disabled. --=20 Simon L. Nielsen --5I6of5zJg18YgZEa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+t/AD8kocFXgPTRwRAkkMAJ0UH/nfGsN9HmUaRL5c/66y0OhsygCfTLit 6tdzwgPQ+tKY4Kmv8Ouav50= =Vfzw -----END PGP SIGNATURE----- --5I6of5zJg18YgZEa--