public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci_set_mwi() ... why isn't it used more?
Date: Mon, 20 Jan 2003 14:00:55 -0500	[thread overview]
Message-ID: <20030120190055.GA4940@gtf.org> (raw)
In-Reply-To: <3E2C42DF.1010006@pacbell.net>

On Mon, Jan 20, 2003 at 10:41:35AM -0800, David Brownell wrote:
> I was looking at some new hardware and noticed that it's
> got explicit support for the PCI Memory Write and Invalidate
> command ... enabled (in part) under Linux by pci_set_mwi().
> 
> However, very few Linux drivers use that routine.  Given
> that it can lead to improved performance, and that devices
> don't have to implement that enable bit, I'm curious what
> the story is...
> 
>  - Just laziness or lack-of-education on the part of
>    driver writers?
> 
>  - Iffy upport in motherboard chipsets or CPUs?  If so,
>    which ones?
> 
>  - Flakey support in PCI devices, so that enabling it
>    leads to trouble?
> 
>  - Something else?
> 
>  - Combination of all the above?

You missed the reason entirely ;-)

pci_set_mwi() is brand new, I just added it.  Hasn't filtered down to
drivers yet.  The few drivers that cared prior to its addition, like
drivers/net/acenic.c, just hand-coded the workarounds needed for proper
MWI support on all chipsets.

pci_set_mwi() would not exist at all, were it not for the existing
hardware quirks.  (if hardware were sane, drivers would just
individually twiddle the _INVALIDATE bit in PCI_COMMAND, and never call
functions other than pci_{read,write}_config_word.

	Jeff




  reply	other threads:[~2003-01-20 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 18:41 pci_set_mwi() ... why isn't it used more? David Brownell
2003-01-20 19:00 ` Jeff Garzik [this message]
2003-01-20 19:37   ` David Brownell
2003-01-30 13:52     ` Anton Blanchard
2003-01-30 16:25       ` David Brownell
2003-01-30 16:59         ` Ivan Kokshaysky
2003-01-30 18:35           ` David Brownell
2003-01-30 23:34             ` Ivan Kokshaysky
2003-01-31  0:11               ` Jeff Garzik
2003-01-31  0:51               ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030120190055.GA4940@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox