----- Original Message -----
From: Der Herr Hofrat <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 11:59 PM
Subject: Re: [rtl] How to have real-time networking
> > Yeah, busy networks are inherently non-real-time. But if you have
> > "complete" control over the traffic, it may be possible to place upper
> > bounds on things like transmission times (assuming a perfect transport
> > layer). Also, it's certainly possible to have a real-time system
> > communicating non-real-time information over a network. It goes in
the
> > category of, "If it's hard real-time, don't do that!"
> >
> one posible solution is to use time-triggert-protocol on a dedicated
> network in that case the physical layer does not bother you as you are
> eliminating collisions in the upper layer - naturally only applicable
> for a dedicated link.
>
> hofrat
>
One solution that the US Military has used for decades is to have a
master-slave arrangement (though they don't use Ethernet) in which no slave
talks unless commanded to by the master. On some networks the role of
master is allowed to be transferred.
Norm
-- [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/
