From: Neil Horman <nhorman@redhat.com>
To: Wes Felter <wesley@felter.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: The ultimate TOE design
Date: Thu, 16 Sep 2004 07:37:16 -0400 [thread overview]
Message-ID: <41497AEC.1010807@redhat.com> (raw)
In-Reply-To: <ciaao4$crc$1@sea.gmane.org>
Wes Felter wrote:
> Neil Horman wrote:
>
>> Paul Jakma wrote:
>>
>>> On Wed, 15 Sep 2004, Jeff Garzik wrote:
>>>
>>>> Put simply, the "ultimate TOE card" would be a card with network
>>>> ports, a generic CPU (arm, mips, whatever.), some RAM, and some
>>>> flash. This card's "firmware" is the Linux kernel, configured to
>>>> run as a _totally indepenent network node_, with IP address(es) all
>>>> its own.
>>>>
>>>> Then, your host system OS will communicate with the Linux kernel
>>>> running on the card across the PCI bus, using IP packets (64K fixed
>>>> MTU).
>
>
>>> The intel IXP's are like the above, XScale+extra-bits host-on-a-PCI
>>> card running Linux. Or is that what you were referring to with
>>> "<cards exist> but they are all fairly expensive."?
>
>
>> IBM's PowerNP chip was also very simmilar (a powerpc core with lots of
>> hardware assists for DMA and packet inspection in the extended
>> register area). Don't know if they still sell it, but at one time I
>> had heard they had booted linux on it.
>
>
> An IXP or PowerNP wouldn't work for Jeff's idea. The IXP's XScale core
> and PowerNP's PowerPC core are way too slow to do any significant
> processing; they are intended for control tasks like updating the
> routing tables. All the work in the IXP or PowerNP is done by the
> microengines, which have weird, non-Linux-compatible architectures.
>
I didn't say the assist hardware wouldn't need an extra driver. Its not
100% free, as Jeff proposes, but the CPU portion of these designs is
_sufficient_ to run linux, and a driver can be written to drive the
remainder of these chips. Its the combination that network device
manufacturers design to today: A specialized chip to do L3/L2 forwarding
at line rate over a large number of ports, and just enough general
purpose CPU to manage the user interface, the forwarding hardware and
any overflow forwarding that the forwarding hardware can't deal with
quickly.
> To do 10 Gbps Ethernet with Jeff's approach, wouldn't you need a 5-10
> GHz processor on the card? Sounds expensive.
>
To handle port densities that are competing in the market today? Yes,
which as I mentioned earlier would price designs like this out of the
market. Jeffs idea is a nice one, but it doesn't really fit well with
the hardware that networking equipment manufacturers are building today.
Take a look at Broadcoms StrataSwitch/StrataXGS lines, or Switchcores
Xpeedium processors. These are the sorts of things we have to work with
. They provide network stack offload in competitive port densities, but
they aren't also general purpose processors. They need a driver to
massage their behavior into something more linux friendly. If we could
develop an infrastrucutre that made these chips easy to integrate into a
platform running linux, linux could quickly come to dominate a large
portion of the network device space.
Neil
> Wes Felter - wesley@felter.org - http://felter.org/wesley/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
next prev parent reply other threads:[~2004-09-16 11:42 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 19:33 The ultimate TOE design Jeff Garzik
2004-09-15 20:04 ` Paul Jakma
2004-09-15 19:14 ` Alan Cox
2004-09-15 20:41 ` Jeff Garzik
2004-09-15 21:01 ` David S. Miller
2004-09-15 21:08 ` Jeff Garzik
2004-09-15 21:13 ` David S. Miller
2004-09-15 21:23 ` Jeff Garzik
2004-09-15 21:29 ` David S. Miller
2004-09-15 22:26 ` Jeff Garzik
2004-09-15 23:29 ` Leonid Grossman
2004-09-24 13:07 ` Lennert Buytenhek
2004-09-24 13:21 ` Leonid Grossman
2004-09-24 18:09 ` Lennert Buytenhek
2004-09-24 19:39 ` Joel Jaeggli
2004-09-16 0:57 ` jamal
2004-09-16 5:25 ` Leonid Grossman
2004-09-16 9:57 ` jamal
2004-09-16 14:57 ` Leonid Grossman
2004-09-16 9:29 ` Lincoln Dale
2004-09-16 12:19 ` Alan Cox
2004-09-16 13:33 ` Andi Kleen
2004-09-16 12:57 ` Alan Cox
2004-09-16 22:37 ` Lincoln Dale
2004-09-17 13:38 ` Jörn Engel
2004-09-15 22:31 ` Jeff Garzik
2004-09-15 21:15 ` Michael Richardson
2004-09-15 20:53 ` David S. Miller
2004-09-16 1:05 ` Andrea Arcangeli
2004-09-15 21:10 ` David Lang
2004-09-15 23:05 ` Paul Jakma
2004-09-15 20:26 ` Neil Horman
2004-09-15 21:03 ` Wes Felter
2004-09-15 21:15 ` Jeff Garzik
2004-09-15 21:35 ` Wes Felter
2004-09-15 21:42 ` Jeff Garzik
2004-09-15 21:25 ` Imran Badr
2004-09-15 21:25 ` Imran Badr
2004-09-16 11:37 ` Neil Horman [this message]
2004-09-16 5:51 ` Matt Porter
2004-09-15 21:36 ` Deepak Saxena
2004-09-15 23:03 ` Paul Jakma
2004-09-24 13:11 ` Lennert Buytenhek
2004-09-15 21:59 ` Tony Lee
2004-09-15 20:11 ` David Stevens
2004-09-15 20:16 ` David Schwartz
2004-09-15 20:25 ` Jeff Garzik
2004-09-15 20:54 ` Neil Horman
2004-09-15 20:31 ` Bill Rugolsky Jr.
2004-09-15 21:41 ` Joel Jaeggli
2004-09-16 6:33 ` Valdis.Kletnieks
2004-09-17 6:46 ` Eric Mudama
2004-09-17 14:15 ` Alan Cox
2004-09-17 20:27 ` Valdis.Kletnieks
2004-09-17 20:36 ` David Lang
2004-09-17 23:20 ` Tony Lee
2004-09-17 23:36 ` Leonid Grossman
2004-09-22 23:25 ` Eric Mudama
2004-09-15 21:36 ` John Heffner
2004-09-15 21:46 ` David S. Miller
2004-09-16 6:20 ` Andi Kleen
2004-09-16 13:10 ` Leonid Grossman
2004-09-16 16:18 ` Nivedita Singhvi
2004-09-16 20:34 ` Leonid Grossman
2004-09-22 20:18 ` Nivedita Singhvi
2004-09-23 4:46 ` Leonid Grossman
2004-09-15 23:16 ` James Morris
2004-09-15 23:37 ` Leonid Grossman
2004-09-15 23:52 ` John Heffner
2004-09-16 1:43 ` James Morris
2004-09-16 9:03 ` Lars Marowsky-Bree
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=41497AEC.1010807@redhat.com \
--to=nhorman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=wesley@felter.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.