From: don-lartc@isis.cs3-inc.com (Don Cohen)
To: lartc@vger.kernel.org
Subject: [LARTC] parallel routers, fast (hardware) traffic split/merge ?
Date: Thu, 21 Nov 2002 16:30:47 +0000 [thread overview]
Message-ID: <marc-lartc-103789654832480@msgid-missing> (raw)
This is not a linux question, but is relevant to the question of how
one might build a fast router out of a large number of processors
running linux.
I imagine a fast link coming to a very simple hardware device
that just distributes the bandwidth equally among a large number
of slower links where they can be routed at lower speeds.
Then we probably need the inverse device that merges a large number
of slow links into one fast one. This seems slightly more complex
in that it requires a little more memory and scheduling.
1. where does one find such split/merge devices?
I suppose they must exist. Cost? References?
2. is this even close to economical ?
Note that it does have one big advantage over commercial routers:
the user can program it.
Which raises
3. are there other fast routers that users can program?
and
4. are devices similar to what I propose already available ?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-11-21 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-103789654832480@msgid-missing \
--to=don-lartc@isis.cs3-inc.com \
--cc=lartc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox