From: Steve Modica <modica@sgi.com>
To: "David S. Miller" <davem@redhat.com>
Cc: johnip@sgi.com, netdev@oss.sgi.com, jgarzik@pobox.com, jes@sgi.com
Subject: Re: Tigon3 5701 PCI-X recv performance problem
Date: Wed, 08 Oct 2003 13:21:50 -0500 [thread overview]
Message-ID: <3F8455BE.8080300@sgi.com> (raw)
In-Reply-To: <20031008101046.376abc3b.davem@redhat.com>
David S. Miller wrote:
> Oh yeah? What are your numbers like if you just disable the ia64
> kernel unaligned access printk()?
Hi David,
it's definitely not the printk. They have that throttled so it only prints once
for a large number of occurances.
The problem is that on the Altix platform they have to deal with unaligned
accesses via an exception handler. This causes them to run through hundreds of
instructions. There's evidntally another mechanism in the cpu that's more
efficient in daling with unaligned accesses, but we can't use that for some
reason (atomicity I think, but I don't recall).
This extra memcpy when the buffer is not unaligned currently only impacts 5701
(since it's the only chip for which the 2 byte pad is omitted) although the
alignment issue would bite us no matter what the chip if the 2 byte pad is omitted.
Steve
--
Steve Modica
work: 651-683-3224
MTS-Technical Lead
"Give a man a fish, and he will eat for a day, hit him with a fish and
he leaves you alone" - me
next prev parent reply other threads:[~2003-10-08 18:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 17:12 Tigon3 5701 PCI-X recv performance problem John Partridge
2003-10-08 17:10 ` David S. Miller
2003-10-08 17:52 ` John Partridge
2003-10-08 18:26 ` David S. Miller
2003-10-08 19:02 ` John Partridge
2003-10-08 19:11 ` Steve Modica
2003-10-08 19:15 ` David S. Miller
2003-10-08 18:21 ` Steve Modica [this message]
2003-10-08 18:29 ` David S. Miller
2003-10-08 18:37 ` Andi Kleen
2003-10-08 19:22 ` David S. Miller
2003-10-08 20:22 ` Andi Kleen
2003-10-08 20:24 ` David S. Miller
2003-10-08 20:33 ` Andi Kleen
2003-10-08 20:32 ` David S. Miller
2003-10-08 20:46 ` Andi Kleen
2003-10-08 20:50 ` David S. Miller
2003-10-10 19:05 ` Steve Modica
2003-10-10 19:20 ` Andi Kleen
2003-10-11 13:17 ` Steve Modica
2003-10-11 13:19 ` Andi Kleen
2003-10-11 17:50 ` David S. Miller
2003-10-13 19:53 ` John Partridge
2003-10-13 19:51 ` David S. Miller
2003-10-14 16:49 ` John Partridge
2003-10-14 16:53 ` David S. Miller
2003-11-11 1:24 ` John Partridge
2003-11-11 2:29 ` David S. Miller
2003-11-11 20:04 ` John Partridge
2003-11-11 20:24 ` David S. Miller
2003-11-11 21:26 ` John Partridge
2003-11-11 21:32 ` Jeff Garzik
2003-12-03 22:11 ` John Partridge
2003-11-11 21:39 ` John Partridge
2003-11-11 23:09 ` David S. Miller
2003-11-11 23:53 ` Andi Kleen
2003-11-12 1:46 ` John Partridge
2003-11-12 6:19 ` Andi Kleen
2003-11-12 7:05 ` Jeff Garzik
2003-11-12 15:32 ` John Partridge
2003-11-12 15:43 ` Christoph Hellwig
2003-11-11 20:25 ` David S. Miller
2003-11-11 20:57 ` Jeff Garzik
2003-10-14 18:47 ` John Partridge
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=3F8455BE.8080300@sgi.com \
--to=modica@sgi.com \
--cc=davem@redhat.com \
--cc=jes@sgi.com \
--cc=jgarzik@pobox.com \
--cc=johnip@sgi.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).