mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] starfire net driver update for 2.4.19pre2
Date: Wed, 06 Mar 2002 17:01:45 -0500	[thread overview]
Message-ID: <3C8691C9.30FA3C29@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203061652050.31906-100000@age.cs.columbia.edu>

Ion Badulescu wrote:
> 
> On Wed, 6 Mar 2002, Jeff Garzik wrote:
> 
> > There is a bugfix, which I will make locally before submitting:
> > PCI_COMMAND_INVALIDATE should be enabled -after- messing with
> > PCI_CACHE_LINE_SIZE.
> 
> I didn't find anything in the starfire chipset's documentation about this,
> so is there a deeper reason for this ordering? As far as I know, most if
> not all x86 PCI chipsets silently map MWI to MW, so it should only matter
> for non-x86 plaforms, right?

More PCI than a Starfire requirement.

And there are plenty of ia32 platforms that benefit from MWI, too. 
Often its server mobos that support MWI, but some cheaper ones do too.


> And, in general, are there any other tricks one can do to speed up the PCI
> transactions on non-x86 platforms? I'm still getting occasional overruns
> on sparc64 (card receiving packets faster than it can push them over PCI),
> which is somewhat disturbing..

Dynamically tune your RX and TX DMA burst settings when you notice these
conditions...  It is indeed possible to saturate PCI bus bandwidth.

	Jeff


-- 
Jeff Garzik      | Usenet Rule #2 (John Gilmore): "The Net interprets
Building 1024    | censorship as damage and routes around it."
MandrakeSoft     |

  reply	other threads:[~2002-03-06 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 21:40 Ion Badulescu
2002-03-06 21:46 ` Jeff Garzik
2002-03-06 21:56   ` Ion Badulescu
2002-03-06 22:01     ` Jeff Garzik [this message]
2002-03-06 22:18     ` David S. Miller
2002-03-07 19:13       ` Ion Badulescu
2002-03-09  3:47       ` David S. Miller

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=3C8691C9.30FA3C29@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=ionut@cs.columbia.edu \
    --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

all inboxes | Powered by JetHome®