From: Chris Wedgwood <cw@f00f.org>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
netdev@oss.sgi.com,
Linux Knernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New net features for added performance
Date: Sun, 25 Feb 2001 16:23:57 +1300 [thread overview]
Message-ID: <20010225162357.A12123@metastasis.f00f.org> (raw)
In-Reply-To: <3A9842DC.B42ECD7A@mandrakesoft.com> <3A986EDB.363639E7@coplanar.net>
In-Reply-To: <3A986EDB.363639E7@coplanar.net>; from jerj@coplanar.net on Sat, Feb 24, 2001 at 09:32:59PM -0500
On Sat, Feb 24, 2001 at 09:32:59PM -0500, Jeremy Jackson wrote:
Related question: are there any 100Mbit NICs with cpu's onboard?
Yes, but the only ones I've seen to date are magic and do special
things (like VPN or hardware crypto). I'm not sure without 'magic'
requirements there is much point for 100M on modern hardware.
Not affordable and whilst moving some of the IP stack onto the card
(I think this is what are alluding to) would be extremely non-trivial
especially if you want all the components (host OS, multiple networks
cards) to talk to each other asynchronously and you would all have to
deal with buggy hardware that doesn't like doing PCI-PCI transfers
and such like.
That said, it would be an extemely neat thing to do from a technical
perspective, but I don't know if you would ever get really good
performance from it.
--cw
next prev parent reply other threads:[~2001-02-25 3:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 23:25 Jeff Garzik
2001-02-24 23:48 ` Andi Kleen
2001-02-25 0:03 ` Jeff Garzik
2001-02-25 0:12 ` Andi Kleen
2000-01-01 0:19 ` Pavel Machek
2001-03-04 1:19 ` LILO error with 2.4.3-pre1 Steven J. Hill
2001-03-04 1:39 ` Keith Owens
2001-03-04 2:27 ` Tom Sightler
2001-03-04 21:32 ` Mircea Damian
2001-03-04 23:05 ` Guest section DW
2001-03-04 2:39 ` Andre Tomt
2001-03-04 3:32 ` Steven J. Hill
2001-03-04 13:35 ` Alan Cox
2001-02-25 0:13 ` New net features for added performance Jeff Garzik
2001-02-25 0:16 ` Andi Kleen
2001-02-25 11:49 ` Rusty Russell
2001-02-25 1:55 ` Michael Richardson
2001-02-25 2:32 ` Jeremy Jackson
2001-02-25 3:23 ` Chris Wedgwood [this message]
2001-02-25 12:41 ` Werner Almesberger
2001-02-25 13:57 ` Chris Wedgwood
2001-02-25 2:38 ` Noah Romer
2001-03-03 23:32 ` Jes Sorensen
2001-02-25 12:01 ` Andrew Morton
2001-02-25 15:11 ` Jeremy Jackson
2001-02-25 12:22 ` Werner Almesberger
2001-03-12 15:08 ` Jes Sorensen
2001-02-25 13:08 ` Jonathan Morton
2001-02-26 23:46 ` David S. Miller
2001-02-27 0:07 ` Jeff Garzik
2001-02-27 0:10 ` David S. Miller
2001-02-26 23:48 ` David S. Miller
2001-02-27 0:03 ` Andi Kleen
2001-02-27 19:59 ` kuznet
2001-02-27 0:08 ` David S. Miller
2001-02-27 2:53 ` Jeremy Jackson
2001-03-01 21:06 ` Jes Sorensen
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=20010225162357.A12123@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=jerj@coplanar.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®