All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 10 Nov 2003 10:35:25 -0700	[thread overview]
Message-ID: <20031110173525.GC24664@colo.lackof.org> (raw)
In-Reply-To: <3F969FFE00009F73@ocpmta2.freegates.net>

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.


> 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?

I don't know. It depends on if/when the misaligned access happens.
It's possible the misaligned access is less expensive than
the full copy on your machine.

grant

  reply	other threads:[~2003-11-10 17:35 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 [this message]
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=20031110173525.GC24664@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.