From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C110 builtin nic slow?
Date: Tue, 11 Nov 2003 12:54:25 +0000 [thread overview]
Message-ID: <3FB0DC01.6070701@tiscali.be> (raw)
In-Reply-To: <20031110173525.GC24664@colo.lackof.org>
Grant Grundler wrote:
> On Mon, Nov 10, 2003 at 03:00:37PM +0100, Joel Soete wrote:
>
>> if (pkt_len > rx_copybreak) {
>> struct sk_buff *newskb;
>
>
> yup - the rx_copybreak support is exactly what I'm talking about.
> tulip driver has similar support.
>
>
>>/* Copy frames shorter than rx_copybreak, otherwise pass on up in
>> * a full sized sk_buff. Value of 100 stolen from tulip.c (!alpha).
>> */
>>static int rx_copybreak = 100;
>
>
> The comment is wrong. Tulip uses 1518 for nearly everything but x86.
> ie it copies all packets since the MTU is <= 1518.
>
Correct :)
I so try rx_copybreak = 1518
and also run from pc netperf (the script
/usr/share/doc/netperf/examples/snapshot_script palin)
but on c110 I noticed many (with rx_copybreak = 100 and rx_copybreak =
1518):
do_page_fault() pid=882 command='netserver' type=15 address=0x0000001c
...
:(
and i never get any miss alignement messages?
I restart this test this morning but in the contrary way ie from c110:
sh /usr/share/doc/netperf/examples/snapshot_script sid.home
then
Netperf snapshot script started at Tue Nov 11 12:52:15 CET 2003
Starting 56x4 TCP_STREAM tests at Tue Nov 11 12:52:52 CET 2003
------------------------------------
Testing with the following command line:
/usr/bin/netperf -t TCP_STREAM -l 60 -H sid.home -i 10,3 -I 99,5 -- -s
57344 -S 57344 -m 4096
seems to send some pkt and finaly hung?
hmm I will try to run it under gdb and so hope to discover what append.
Cheers,
Joel
next prev parent reply other threads:[~2003-11-11 12:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 11:10 [parisc-linux] C110 builtin nic slow? 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 [this message]
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:22 ` [parisc-linux] Dual NICs on 9000/715, anyone? buggz
2003-11-15 23:34 ` Matthew Wilcox
2003-11-15 23:50 ` buggz
2003-11-16 1:51 ` Grant Grundler
2003-11-16 4:16 ` Shane G. Brodie
2003-11-16 4:32 ` Grant Grundler
2003-11-15 23:58 ` [parisc-linux] C110 builtin nic slow? 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
-- strict thread matches above, loose matches on Subject: below --
2003-10-26 16:49 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
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=3FB0DC01.6070701@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.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