From owner-freebsd-current@FreeBSD.ORG  Fri May 11 03:12:34 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 62C8816A402
	for <freebsd-current@freebsd.org>; Fri, 11 May 2007 03:12:34 +0000 (UTC)
	(envelope-from scottl@samsco.org)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.freebsd.org (Postfix) with ESMTP id 1A8ED13C447
	for <freebsd-current@freebsd.org>; Fri, 11 May 2007 03:12:34 +0000 (UTC)
	(envelope-from scottl@samsco.org)
Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l4B3CVp5021844
	for <freebsd-current@freebsd.org>; Thu, 10 May 2007 21:12:31 -0600 (MDT)
	(envelope-from scottl@samsco.org)
Message-ID: <4643DF1A.7080906@samsco.org>
Date: Thu, 10 May 2007 21:12:26 -0600
From: Scott Long <scottl@samsco.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
	rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <20070511021015.GF21472@obelix.dsto.defence.gov.au>
	<868xbwyu3i.wl%rpaulo@fnop.net> <86vef0oz1e.wl%rpaulo@fnop.net>
	<20070511030604.GG22064@obelix.dsto.defence.gov.au>
In-Reply-To: <20070511030604.GG22064@obelix.dsto.defence.gov.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]);
	Thu, 10 May 2007 21:12:31 -0600 (MDT)
X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed
	version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org
Subject: Re: Message Signalled Interrupts Question ...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2007 03:12:34 -0000

Wilkinson, Alex wrote:
>     0n Fri, May 11, 2007 at 03:49:01AM +0100, Rui Paulo wrote: 
> 
> bge(4) has MSI support but not em(4) ... bizarre.
> 
>   bge0@pci5:2:0:  class=0x020000 card=0x12bc103c chip=0x169614e4 rev=0x03 hdr=0x00
>       vendor     = 'Broadcom Corporation'
>       device     = 'BCM5782 Broadcom NetXtreme Gigabit Ethernet for hp'
>       class      = network
>       subclass   = ethernet
>       cap 01[48] = powerspec 2  supports D0 D3  current D0
>       cap 03[50] = VPD
>       cap 05[58] = MSI supports 8 messages, 64 bit 
>   em0@pci5:4:0:   class=0x020000 card=0x10018086 chip=0x10268086 rev=0x04 hdr=0x00
>       vendor     = 'Intel Corporation'
>       device     = '82545GM Gigabit Ethernet Controller'
>       class      = network
>       subclass   = ethernet
>       cap 01[dc] = powerspec 2  supports D0 D3  current D0
>       cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction
> 
>  -aW
> 

Beware that just because a chip reports MSI support doesn't mean that it
actually works.  MSI is still relatively new technology, and one that is
only recently getting real-world testing and validation.  We will be
adding and maintaining driver quirks to selectively disable MSI for a
long time to come.

Scott