From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ns83820 0.17
Date: 12 Mar 2002 13:12:32 -0500 [thread overview]
Message-ID: <1015956757.4220.3.camel@aurora> (raw)
In-Reply-To: <20020312.031509.53067416.davem@redhat.com>
In-Reply-To: <20020312004036.A3441@redhat.com> <51A3E836-35A8-11D6-A4A8-000393843900@metaparadigm.com> <20020312.031509.53067416.davem@redhat.com>
On Tue, 2002-03-12 at 06:15, David S. Miller wrote:
> Use a cross-over cable to play with Jumbo frames, that is
> what I do :-)
>
> Later this week I'll rerun tests on all the cards I have
> (Acenic, Sk98, tigon3, Natsemi etc.) with current drivers
> to see what it looks like with both jumbo and non-jumbo
> mtus over gigabit.
I no longer have the original, so I will just have to respond to this
one, since it is related. I know I know nearly nothing about
networking, but here has been my thinking.
David, you believe we don't need NAPI. You believe we perform fine
without it. Here is my question. A PCI bus, IRC, has about 500
Megabytes/sec of bandwidth. A full blown gigabit Ethernet stream should
be around 133 Megabytes/sec. Sounds to me like a PC could act easily
(As far as bandwidth is concerned) as a 4 to 5 port gigabit Ethernet
router.
How well does this work with NAPI and how well does it work without? Is
NAPI a gain here?
Maybe there are other issues involved that I am unaware of, if there
are, I would still like to see how the theoretical answers pan out.
Thank you,
Trever Adams
next prev parent reply other threads:[~2002-03-12 18:12 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 12:58 Broadcom 5700/5701 Gigabit Ethernet Adapters Frank Elsner
2002-02-15 13:06 ` Jeff Garzik
2002-02-15 14:36 ` Thomas Langås
2002-02-15 14:45 ` Jeff Garzik
2002-02-15 14:55 ` Thomas Langås
2002-02-15 15:00 ` Jeff Garzik
2002-02-15 15:36 ` Thomas Langås
2002-02-15 20:20 ` David S. Miller
2002-02-19 0:18 ` Thomas Langås
2002-02-15 15:03 ` Jason Lunz
2002-02-26 20:09 ` Jes Sorensen
2002-02-15 14:43 ` J Sloan
2002-02-27 14:12 ` Stephan von Krawczynski
2002-03-10 15:33 ` Harald Welte
2002-03-10 19:10 ` Jeff Garzik
2002-03-10 21:35 ` Harald Welte
2002-03-11 0:41 ` David S. Miller
2002-03-11 0:55 ` Richard Gooch
2002-03-11 1:03 ` David S. Miller
2002-03-11 1:14 ` Richard Gooch
2002-03-11 1:31 ` David S. Miller
2002-03-11 1:31 ` Jeff Garzik
2002-03-11 2:05 ` Wayne Whitney
2002-03-11 2:04 ` David S. Miller
2002-03-11 2:10 ` Richard Gooch
2002-03-11 2:15 ` David S. Miller
2002-03-11 2:22 ` Benjamin LaHaise
2002-03-11 2:28 ` Mike Fedyk
2002-03-11 2:32 ` David S. Miller
2002-03-11 2:30 ` David S. Miller
2002-03-11 3:15 ` Benjamin LaHaise
2002-03-11 4:20 ` Michael Clark
2002-03-11 4:28 ` Benjamin LaHaise
2002-03-11 19:48 ` Richard Gooch
2002-03-12 6:04 ` David S. Miller
2002-03-12 6:20 ` Richard Gooch
2002-03-12 5:40 ` [patch] ns83820 0.17 (Re: Broadcom 5700/5701 Gigabit Ethernet Adapters) Benjamin LaHaise
2002-03-12 11:00 ` Michael Clark
2002-03-12 11:15 ` [patch] ns83820 0.17 David S. Miller
2002-03-12 13:03 ` dean gaudet
2002-03-12 13:03 ` David S. Miller
2002-03-12 18:12 ` Trever L. Adams [this message]
2002-03-12 18:17 ` David S. Miller
2002-03-12 18:31 ` Trever L. Adams
2002-03-12 19:52 ` pjd
2002-03-12 19:06 ` Charles Cazabon
2002-03-12 19:39 ` Pedro M. Rodrigues
2002-03-14 9:54 ` [patch] ns83820 0.17 (Re: Broadcom 5700/5701 Gigabit Ethernet Adapters) Jeff Garzik
2002-03-14 20:37 ` Benjamin LaHaise
2002-03-15 1:02 ` Jeff Garzik
2002-03-15 8:56 ` Daniel Phillips
2002-04-08 5:14 ` Richard Gooch
2002-03-11 2:04 ` Broadcom 5700/5701 Gigabit Ethernet Adapters Ben Collins
2002-03-11 2:13 ` David S. Miller
2002-03-11 2:22 ` Ben Collins
2002-03-11 2:31 ` David S. Miller
2002-03-21 20:39 ` Thomas Langås
2002-03-11 6:07 ` Harald Welte
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=1015956757.4220.3.camel@aurora \
--to=tadams-lists@myrealbox.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 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.