[ltt-dev] UST communication library
yannick.brosseau at gmail.com
Wed Jun 15 11:16:30 EDT 2011
On 2011-06-15 11:13, David Goulet wrote:
> On 11-06-15 11:06 AM, Yannick Brosseau wrote:
> > On 2011-06-14 17:26, David Goulet wrote:
> >> Hi everyone,
> >> We are in the process of moving out the UST control library out to
> >> (thus soon deprecating ustctl and usttrace from the UST git tree).
> >> there is a common part which is the communication library
> (libustcomm) where
> >> every command to the tracer and responses are done through a Unix
> socket using
> >> that specific libs (that contains key functions to pack/unpack data).
> >> So the problem is where this lib should go? Here are the
> possibilities I've
> >> discussed with Mathieu:
> > 7) Define a communication protocol and implement it on both side. That
> > way, you have to library to depends on.
> This is a re-write of the actual code (will be the third time), code
> across two git tree and handling data function will be the same both
> sides since
> it's a bidirectional communication. I really think it's not the best
> way to do
With our architecture, there is not code duplication, because it's not a
generic bidirectional communication. Some message goes in our directions
and some other in the other.
The controller and the "provider" each use their own part of the library
(it there is a library)
More information about the lttng-dev