From owner-freebsd-performance@FreeBSD.ORG Mon Mar 3 22:38:59 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 400D61065676 for ; Mon, 3 Mar 2008 22:38:59 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-72-87-39-191.ptldor.fios.verizon.net [72.87.39.191]) by mx1.freebsd.org (Postfix) with ESMTP id 178798FC2D for ; Mon, 3 Mar 2008 22:38:58 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.2/8.13.8) with ESMTP id m23McwDG017431 for ; Mon, 3 Mar 2008 14:38:58 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.2/8.14.1/Submit) with UUCP id m23McwBU017427 for freebsd-performance@freebsd.org; Mon, 3 Mar 2008 14:38:58 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id VAA08472; Mon, 3 Mar 2008 21:34:00 GMT Message-Id: <200803032134.VAA08472@sopwith.solgatos.com> To: freebsd-performance@freebsd.org In-reply-to: Your message of "Mon, 03 Mar 2008 08:42:03 GMT." Date: Mon, 03 Mar 2008 13:34:00 +0000 From: Dieter Subject: Re: PCIe vs PCI (was: Re: FreeBSD bind performance in FreeBSD 7) X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 22:38:59 -0000 > Is there a way to tell from dmesg or pciconf that something is > PCIe rather than PCI? The onboard stuff could be either. The secret appears to be pciconf -l -v | grep -i express device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' This bge(4) Broadcom chip had problems in 6.0 but works well in 6.2. The critical part for my application is not getting the maximum number of packets per second, but in not dropping any, and getting them acked rapidly. The closed source "black box" on the other end of the wire has a buggy network stack, a *way* too small transmit buffer, and generates data in real time that I have only one chance to capture. The remaining problem is that other device drivers can lock it out. For example: http://www.freebsd.org/cgi/query-pr.cgi?pr=118093