From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: ionut@cs.columbia.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] starfire net driver update for 2.4.19pre2
Date: Wed, 06 Mar 2002 14:18:09 -0800 (PST) [thread overview]
Message-ID: <20020306.141809.112819805.davem@redhat.com> (raw)
In-Reply-To: <3C8691C9.30FA3C29@mandrakesoft.com>
In-Reply-To: <Pine.LNX.4.44.0203061652050.31906-100000@age.cs.columbia.edu> <3C8691C9.30FA3C29@mandrakesoft.com>
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Date: Wed, 06 Mar 2002 17:01:45 -0500
> 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.
On sparc64 you should set the burst settings to 64-byte read/write
bursts because the PCI chipset is going to disconnect you on 64-byte
boundaries anyways. If the chip is bursting more than this, you
are wasting lots of PCI cycles with the retries done after the
disconnect.
Also make sure to use PCI READ MULTIPLE commands for DMA if the chip
provides such an option, this helps performance on many PCI
controllers to no end.
next prev parent reply other threads:[~2002-03-06 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 21:40 [PATCH] starfire net driver update for 2.4.19pre2 Ion Badulescu
2002-03-06 21:46 ` Jeff Garzik
2002-03-06 21:56 ` Ion Badulescu
2002-03-06 22:01 ` Jeff Garzik
2002-03-06 22:18 ` David S. Miller [this message]
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=20020306.141809.112819805.davem@redhat.com \
--to=davem@redhat.com \
--cc=ionut@cs.columbia.edu \
--cc=jgarzik@mandrakesoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.