[EMAIL PROTECTED] wrote:
>
> Depends on what you want to do. I think RT/Beowulf is a natural combination
> for systems where, for example, one needs a supercomputer level of
> visualization or simulation connected to RT control.
And while we're on the Beowulf subject; what's the latest news in the
network
drivers/RTLinux area? I have seen some interesting documents on RETHER,
but
I'd like to see some more figures on actual transfer rates and latencies
that
can be achieved with RTLinux drivers.
What I'm after is how low a total latency can be achieved in a system
(signal
processing network) where RT tasks are distributed over the nodes in a
Beowulf
class cluster. (100 Mb or gigabit ethernet to connect the nodes.)
It has been suggested to me that a Beowulf could never handle lower
total
processing latency (ie from signal input to output) than some 100 ms,
but I
find that hard to believe, at least for the application I have in mind.
Unless
ethernet _hardware_ is limited to latencies in the 10-100 ms range, I
can't
see a real problem here...
So, can ethernet hardware + RTL drivers do the job, or are the only
options
still SMP or real shared memory network hardware? (I've seen some notes
about
results from various sources, but I'm still lacking a clear picture of
the
situation.)
//David
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
