[RTEMS Project] #3695: Add UDP transfer of event recording data
RTEMS trac
trac at rtems.org
Thu Feb 21 06:23:49 UTC 2019
#3695: Add UDP transfer of event recording data
-----------------------------+------------------------------
Reporter: Sebastian Huber | Owner: Sebastian Huber
Type: project | Status: assigned
Priority: normal | Milestone:
Component: tool | Version:
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------------
Comment (by Sebastian Huber):
Replying to [comment:1 Chris Johns]:
> Replying to [ticket:3695 Sebastian Huber]:
> > The TCP is sometimes not the best choice to transfer this information.
A UDP transfer should be added on a best effort basis, e.g. lost packages
are not retransmitted.
>
> Are we converging on the need for a common transport interface and
service? I have this interface in libdebugger ...
>
> https://git.rtems.org/rtems/tree/cpukit/include/rtems/debugger/rtems-
debugger-remote.h
>
> I would welcome UDP, termios, bare BSP IO, even USB. I am fine with this
interface moving and growing.
It should be suitable as a GSoC project. Designing such a more general
purpose interface needs a lot of experience.
One option is to simply connect to the lttng tools, e.g.
[https://lttng.org/man/8/lttng-relayd lttng-relayd].
> > The receiver should hand over the package loss information to
potential high level consumers.
>
> I do not understand this sentence.
>
> With UDP a 32bit value at the start is worth the extra overhead. A few
high order bits can be flags, for example overflow, resync, etc and the
remainder a sequence number to let the remote know if data has been lost.
For the receiver, it should be clear if the data loss happens because the
target ring buffer overflowed or packets are lost during transport.
--
Ticket URL: <http://devel.rtems.org/ticket/3695#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list