Le 2013-03-25 11:58, Geneviève Bastien a écrit :
> Hi all,
>
> As trace analysis tools become available in TMF (trace
> synchronization, critical path calculation, latency, etc), a
> requirement is to be able to express dependencies between events.
As for the critical path, I'm working on a flat v
Hi Bernd,
Thanks for your feedback.
On 03/26/2013 10:08 AM, Bernd Hufmann wrote:
Hi Geneviève
Please see below.
BR,
Bernd
On Mon, Mar 25, 2013 at 11:58 AM, Geneviève Bastien
wrote:
The dependency graph could be displayed also as a sequence diagram. It could
also be exported as a dot file
Hi Michel,
Thanks for your feedback.
I'd propose to use a graph structure to represent those dependencies
(a set of vertices - an object at a given timestamp - and edges - a link
between two vertices).
Do the "vertices" already exist or you plan to "add" new objects. Currently,
events in the
Hi Geneviève
Please see below.
BR,
Bernd
On Mon, Mar 25, 2013 at 11:58 AM, Geneviève Bastien
wrote:
> Hi all,
>
> As trace analysis tools become available in TMF (trace synchronization,
> critical path calculation, latency, etc), a requirement is to be able to
> express dependencies between eve
> As trace analysis tools become available in TMF (trace synchronization,
> critical path calculation, latency, etc), a requirement is to be able to
> express dependencies between events.
Yes, an example is a process A writing to a pipe to send a request to process
B, and waiting and receiving
Hi all,
As trace analysis tools become available in TMF (trace synchronization,
critical path calculation, latency, etc), a requirement is to be able to
express dependencies between events.
After discussions and seeing the work done so far on trace analysis,
here is a proposal for how to exp
