From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C110 builtin nic slow?
Date: Sun, 9 Nov 2003 21:36:54 -0700 [thread overview]
Message-ID: <20031110043654.GA16478@colo.lackof.org> (raw)
In-Reply-To: <3F9C3154.4060105@tiscali.be>
On Sun, Oct 26, 2003 at 08:40:52PM +0000, Joel Soete wrote:
> hmm may be should I try to rebuild the very last src (from hp).
netperf home is netperf.org.
> More over the pkg is not available for parisc but I trust it would just
> be rebuild for this platform?
It does run/build on parisc. I've used it before.
Note that with B180, I can only get about 1MB/s throughput max.
With C3000 I get about 5 or 6 MB/s 100BT link.
Your network performance numbers are pretty far off from that
but there might be other factors involved.
I expect mem copy routines are saturating the CPU and thrashing
the data cache. The tulip driver copies the entire buffer from
where the card DMA'd to the skbuff in order to "bias" the buffer
by 2 bytes. This avoids un-aligned data access in the "common" TCP case.
Adding "unaligned access" macros to the "common" networking code
path has been discussed and rejected (again) in the past month or so.
Linus himself has rejected such proposals in the past too.
If you twiddle the tulip driver to NOT copy all the data for
packets > 512 bytes, the kernel will tell you when/where the network
stack makes unaligned accesses. You can fix those and keep that as
a local patch. I'd be interested in hearing the netperf (or httperf)
numbers with such a patch when compared to the current behavior.
thanks,
grant
next prev parent reply other threads:[~2003-11-10 4:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 16:49 [parisc-linux] C110 builtin nic slow? Joel Soete
2003-10-26 17:25 ` Grant Grundler
2003-10-26 20:40 ` Joel Soete
2003-10-26 21:10 ` Joel Soete
2003-10-27 19:39 ` Grant Grundler
2003-10-27 20:13 ` Matthew Wilcox
2003-10-28 8:39 ` Joel Soete
2003-10-28 19:32 ` Joel Soete
2003-10-28 19:34 ` Matthew Wilcox
2003-10-29 6:43 ` Joel Soete
2003-11-10 4:36 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 11:10 Joel Soete
2003-11-10 12:31 ` Joel Soete
2003-11-10 14:00 ` Joel Soete
2003-11-10 17:35 ` Grant Grundler
2003-11-11 12:54 ` Joel Soete
2003-11-12 3:22 ` Grant Grundler
2003-11-15 19:41 ` Joel Soete
2003-11-15 22:56 ` M. Grabert
2003-11-15 23:58 ` M. Grabert
2003-11-16 17:00 ` Joel Soete
2003-11-21 21:44 ` Joel Soete
2003-11-21 22:37 ` Joel Soete
2003-11-16 16:53 ` Joel Soete
2003-11-10 17:37 ` Grant Grundler
2003-11-10 19:23 ` Joel Soete
2003-11-10 20:38 ` Joel Soete
2003-11-11 1:31 ` M. Grabert
2003-11-11 11:45 ` Joel Soete
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=20031110043654.GA16478@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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.