Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 13 Feb 2001 15:30:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 13 Feb 2001 15:29:49 -0500 Received: from vp175097.reshsg.uci.edu ([128.195.175.97]:61703 "EHLO moisil.dev.hydraweb.com") by vger.kernel.org with ESMTP id ; Tue, 13 Feb 2001 15:29:27 -0500 Date: Tue, 13 Feb 2001 12:29:16 -0800 Message-Id: <200102132029.f1DKTGM01731@moisil.dev.hydraweb.com> From: Ion Badulescu To: Jeff Garzik Cc: Gerard Roudier , Alan Cox , Donald Becker , Linux-Kernel , Jes Sorensen Subject: Re: [PATCH] starfire reads irq before pci_enable_device. In-Reply-To: User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.2.18 (i586)) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 13 Feb 2001 07:06:44 -0600 (CST), Jeff Garzik wrote: > On 12 Feb 2001, Jes Sorensen wrote: >> In fact one has to look out for this and disable the feature in some >> cases. On the acenic not disabling Memory Write and Invalidate costs >> ~20% on performance on some systems. > > And in another message, On Mon, 12 Feb 2001, David S. Miller wrote: >> 3) The acenic/gbit performance anomalies have been cured >> by reverting the PCI mem_inval tweaks. > > Just to be clear, acenic should or should not use MWI? > > And can a general rule be applied here? Newer Tulip hardware also > has the ability to enable/disable MWI usage, IIRC. And so do eepro100 and starfire. On the eepro100 we're enabling MWI unconditionally, and on the starfire we disable it unconditionally... I should probably take a look at acenic's use of PCI_COMMAND_INVALIDATE to see when it gets activated. Some benchmarking would probably help, too -- maybe later today. Ion -- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/