Linux PARISC architecture development
 help / color / mirror / Atom feed
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: Mon, 10 Nov 2003 15:00:37 +0100	[thread overview]
Message-ID: <3F969FFE00009F73@ocpmta2.freegates.net> (raw)
In-Reply-To: <3F969FFE00009EA4@ocpmta2.freegates.net>

Grant,

Sorry again, but having find this interesting stuff in 82596.c:
---------><---------
[...]
                        /* Check if the packet is long enough to just accept
                         * without copying to a properly sized skbuff.
                         */

                        if (pkt_len > rx_copybreak) {
                                struct sk_buff *newskb;
[...]
                        }
                        else
                                skb = dev_alloc_skb(pkt_len + 2);

[...]
---------><---------
This seems well what you describe?
and more:
---------><---------
[...]
/* 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;
[...]
---------><---------
and finaly:
---------><---------
/*
[...]
   TBD:
   [...]
   * performace test to tune rx_copybreak
[...]
---------><---------

(I just copy as read preformace and not performance as my mind abuse :) )

This last notice seems what I am loocking for?
Have you a better idea then try and test (ie rx_copybreak=512, test, rx_copybreak=256,
... and btw rx_copybreak = PKT_BUF_SZ == 1536)?
Or is it better to tiddle code before?

Thanks for additional advise,
    Joel

>-- Original Message --
>From: "Joel Soete" <soete.joel@tiscali.be>
>To: "Grant Grundler" <grundler@parisc-linux.org>
>Cc: "parisc-linux" <parisc-linux@lists.parisc-linux.org>
>Date: Mon, 10 Nov 2003 13:31:45 +0100
>Subject: Re: [parisc-linux] C110 builtin nic slow?
>
>
>Sorry for auto-reply but I just remember that on the c110 the builtin nic
is:
"8. Raven T' Core LAN (802.3) (10) at 0xffd07000 [8/16/6], versions 0x32,

0x0, 0x8a"
ie a Lasi_82596 (as Matthew mentioned in a previous mail).

That you look for tha
> stuff in that code :)

Joel




-------------------------------------------------------------------------
Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde.

http://reg.tiscali.be/default.asp?lg=fr

  reply	other threads:[~2003-11-10 14:00 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 [this message]
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: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=3F969FFE00009F73@ocpmta2.freegates.net \
    --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