Two Ethernet or One?

On 29 sep, 10:09, "Sink0" <sink00@n_o_s_p_a_m.gmail.com> wrote:
> >On 29.09.2010 11:11, Sink0 wrote:
>
> >> I may be saying something stupid, but how he can control the band
> sharing
> >> among both (debug and control/data)?
>
> >That's what you have an operating system and its TCP/IP stack for, among
> >other things. =A0No need to re-invent every single wheel in the universe=
.
>
> >> Using one connection would reduce the
> >> data trhoughtput no?
>
> >It might. =A0But he didn't give any believable indication of being so
> >severely bandwidth limited that that would actually make a difference.
> >Frankly, if had managed to saturate a 100Mb/s or faster Ethernet link
> >with payload data, he would surely be well beyond asking the kind of
> >questions he does.
>
> >> That could lead to a non real-time behavior.
>
> >All debugging usually does that.
>
> Very good answers but the first. I think you did not understand my point
> and it is pure ignorance of my part. Is there any way to hard share the
> network band, something like this port CANT at any moment use more than
> certain amount of the band? Probably there is someway on how to do that, =
i
> just dont know how.
>
> But after all the answers...yes, one ethernet would be the best option i
> think. =A0 =A0
>
> --------------------------------------- =A0 =A0 =A0 =A0
> Posted throughhttp://www.EmbeddedRelated.com

I think you can create as many limits on bandwidth over ports,
applications, etc as your OS allows you to.
Regarding real time beahvior: TCP/IP is not intended for real time
applications. If you mean "human" real time then you don't even have
worry for debug signals since they're narrowband compared to -for
instance- media streaming.