Yusuf Motiwala <[EMAIL PROTECTED]> writes:
> I think that keeping the networking portion as a part of the non-realtime
> task (kernel) running at low priority is not a good idea. Now days, many (most)
>
> of the real-time systems depending upon the network connectivity. Making
> networking stack as low priority task will result in a non-reliable
> communication.
> Also, may systems are designed to provide the connectivity, say routers. Ffor
> such
> system, this approach is highly un-reliable. May be I am wrong, but in that
> case pls
> correct me.
>
> Regards,
> Yusuf
I agree, but what can I do until RTL gets some RT networking support?
I don't have those Tulip NICs; maybe I can ask managers to buy some...
Another problem is that my client programs run on non-RT machines (so,
at this point, all I am interested in is a relatively high, stable
throughput, not more than that)...
My answer to the other people who responded (thanks!) is somewhat
similar. I need lossless transfer because I send large images for
processing a couple of times per second, and smaller ones (10kB on
average) more often (it's not JPEG but some raw image format; JPEG
encoding/decoding would be too costly). Based on some previous ATM
experience, and other people's experience with 100Mbps Ethernet, I
thought I could achieve certain throughput. Now, sometimes I get some
reasonable results, sometimes something goes wrong. In particular,
what could make a non-blocking "send" (socket) call take 16 seconds???
(I used the TCP NODELAY option to make it non-blocking. Is there a
better one?) I've been getting different results with different
machines as senders and receivers; so far, not so good.
Thanks,
Aleks
--- [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/
