From owner-freebsd-stable@FreeBSD.ORG Mon Aug 26 09:28:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 856DB320; Mon, 26 Aug 2013 09:28:58 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB5AE2BC0; Mon, 26 Aug 2013 09:28:56 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r7Q9Sqtm024928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Aug 2013 11:28:53 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <521B1FD4.4050702@omnilan.de> Date: Mon, 26 Aug 2013 11:28:52 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: if_em, legacy nic and GbE saturation References: <521AFE7E.2040705@omnilan.de> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0C892B502D9084CC08DA245B" Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2013 09:28:58 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0C892B502D9084CC08DA245B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Bez=FCglich Adrian Chadd's Nachricht vom 26.08.2013 10:34 (localtime): > Hi, > > There's bus limits on how much data you can push over a PCI bus. You > can look around online to see what 32/64 bit, 33/66MHz PCI throughput > estimates are. > > It changes massively if you use small versus large frames as well. > > The last time I tried it i couldn't hit gige on PCI; I only managed to > get to around 350mbit doing TCP tests. Thanks, I'm roughly aware about the PCI bus limit, but I guess it should be good for almost GbE: 33*10^6*32=3D1056, so if one considers overhead and other bus-blocking things (nothing of significance is active on the PCI bus in this case), I'd expect at least 800Mbis/s, which is what I get with jumbo frames. I also know that lagg won't help in regard of concurrent throughput because of the PCI limit. But it's the redundancy why I also use 2 nics in that parking-maschine. I just have no explanation why I see that noticable difference between mtu 1500 and 9000 on legacy if_em nic, which doesn't show up with the second on-board nic (82566), which uses different if_em code. I can imagine that it's related to PCI transfer limits (the 82566 is ICH9 integrated which connects via DMI to the CPU, so no PCI constraint), but if someone has more than an imagination, an explanation was highly appreciated :-) But if you saw similar constraints on other (non-if_em?) PCI-connected nics, I'll leave it as it is. Just wanted some kind of confirmation that it's normal that single-GbE doesn't play well with PCI. Thank you, -Harry --------------enig0C892B502D9084CC08DA245B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlIbH9QACgkQLDqVQ9VXb8iWmgCfenebOJrkeWbv5ux+hlg3Cwt5 400AnRfeET7T6kwHzFoH8HwmCLTOXyUF =Vf8y -----END PGP SIGNATURE----- --------------enig0C892B502D9084CC08DA245B--