Our application must process messages generated from various
network nodes and transmitted over Ethernet.
We have calculated that we will have 57,600 messages per second,
at 368 bits per message. We're using raw Ethernet frames (no TCP/IP.)
This comes out to 21,119,800 bits per second -- i.e. around 20MBit/sec.
We're using a 100bT Ethernet LAN, so the raw bandwidth (we think) should
be under control. However, each of these 57,600 messages must be
actually processed by various (generally small) "protection algorithms."
Most messages require no response but some may indicate a fault
and need to be responded to.
We're currently attempting to do this on a 1000MHz Pentium III box.
Turnaround time for any given message that requires a response can
be no greater than 2 milliseconds. (It occurred to me the other day
that we are more or less being asked to build an oscilloscope that
listens over Ethernet. :)
This is just a general question; I'm attempting to draw on the expertise
of the group. Do we have a snowball's chance in Hades of pulling this
off w/ RTLinux? :) Any suggestions or pitfalls? ("You need a dual processor
box." "Don't shoot yourself in the foot by doing Foo.")
Any and all thoughts and comments are welcome.
Thanks in advance!!
Dan Morrill
Computer Scientist
GE Corporate R&D
*****************************
My opinions are my own, and may not reflect those of my employer..
----- End of forwarded message from [EMAIL PROTECTED] -----
-- [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/
