<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Divya,<br>
<br>
I'm bringing this discussion back to lttng-dev, as it may benefit
others in the future. <br>
<br>
You now have the right fields to synchronize traces. It uses
packets of type TCP and fields seq, ack_seq and flags to match
packets.<br>
<br>
But what are you trying to achieve exactly? The traces you sent me
are taken on the same machine at different times. They can never
be synchronized. Trace synchronization allows you to synchronize
traces taken at the same time on different machines (clocks) so
that their events can have the same reference clock.<br>
<br>
You can apply a time offset to one of the traces so that their
beginning matches (Right-click on the experiment -> Apply time
offset... More documentation on this feature is available in the
master code). If that's what you want. Otherwise, please explain
your specific need.<br>
<br>
Geneviève<br>
<br>
<br>
On 01/06/2015 01:33 AM, Divya Vyas wrote:<br>
</div>
<blockquote
cite="mid:CA+=dQ-8oGmyKDfNEfLwu_WLeouu0XXxQVigciVBDV3T6dQJ+pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hi,<br>
<br>
</div>
I am attaching the traces . I tried to synchronize the traces
of same machine but still quality is absent . <br>
<br>
</div>
I am in urgent need to get these traces synchronized . <br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jan 6, 2015 at 11:00 AM, Divya
Vyas <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:dvyas@mvista.com" target="_blank">dvyas@mvista.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>Hi ,<br>
<br>
</div>
I tried again the steps.<br>
<br>
net_dev_queue: { cpu_id = 0 }, { skbaddr =
18446612135892807424, len = 98, name = "eth0",
network_header = ( _nhtype_ip : container = 1 ),
network_fields = { nhtype_ip = { ihl_version = 0x45, tos
= 0, tot_len = 84, id = 0x560A, frag_off = 16384, ttl =
64, protocol = 0x1, checksum = 0xFFF4, saddr =
0xAA267D8, daddr = 0xAA2678E } }, transport_header = (
_thtype_none : container = 0 ), transport_fields = {
thtype_none = { } } }<br>
<br>
net_dev_queue: { cpu_id = 0 }, { skbaddr =
18446612135892807424, len = 98, name = "eth0",
network_header = ( _nhtype_ip : container = 1 ),
network_fields = { nhtype_ip = { ihl_version = 0x45, tos
= 0, tot_len = 84, id = 0x560A, frag_off = 16384, ttl =
64, protocol = 0x1, checksum = 0xFFF4, saddr =
0xAA267D8, daddr = 0xAA2678E } }, transport_header = (
_thtype_none : container = 0 ), transport_fields = {
thtype_none = { } } }<br>
<br>
<br>
</div>
Is this kind of data should be added in the trace log ? <br>
<br>
<br>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jan 6, 2015 at 3:21
AM, Divya Vyas <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:dvyas@mvista.com" target="_blank">dvyas@mvista.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Hi,</p>
<p dir="ltr">Can you please help me what kind of
extra fields will be added in trace data.
Because I think I followed all the steps. </p>
<p dir="ltr">The branch I was not able to got
,getting some git error. So I downloaded
snapshot from website.</p>
<div>
<div>
<div class="gmail_quote">On Jan 5, 2015 9:14
PM, "Geneviève Bastien" <<a
moz-do-not-send="true"
href="mailto:gbastien@versatic.net"
target="_blank">gbastien@versatic.net</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Divya,<br>
<br>
I looked at your traces and you do not
seem to be using the
'net_data_experimental' special branch
to get the extra fields for
synchronization. You have the
net_dev_queue and netif_receive_skb
events, but they do not have the
required fields to be able to
synchronize. See the section "Obtain
synchronizable traces" in <a
moz-do-not-send="true"
href="http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.linuxtools.lttng.help%2Fdoc%2FTrace-synchronization.html"
target="_blank">http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.linuxtools.lttng.help%2Fdoc%2FTrace-synchronization.html</a>
for how to compile with that branch.<br>
<br>
Geneviève<br>
<br>
<br>
On 12/28/2014 12:44 AM, Divya Vyas
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Hi,<br>
<br>
</div>
I am getting Synchronization
quality is absent. The
workload I am using is ssh and
scp . <br>
<br>
</div>
I have attached the traces . Can
you please look at it and give
em some advise where I am going
wrong? <br>
<br>
</div>
Thanks,<br>
</div>
Divya<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec
24, 2014 at 1:54 AM, Geneviève
Bastien <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:gbastien@versatic.net"
target="_blank">gbastien@versatic.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Hi
Divya,<br>
<br>
If you followed the instructions
in the help, then you have
compiled<br>
LTTng-modules with the right
tracepoints enabled on all the
machines you<br>
want to synchronize. Which
method did you choose?<br>
<br>
Make sure you enabled either
net_dev_queue/netif_receive_skb
or<br>
inet_sock_local_in/inet_sock_local_out
on all machines. Also make sure<br>
all machines exchange TCP
packets during the trace,
otherwise there will<br>
be nothing to synchronize them
on.<br>
<br>
When you say you are not getting
anything, what do you mean? Do
you have<br>
output in the Synchronization
view? If the synchronization was
OK, but<br>
nothing was found, you should
get a Synchronization Quality of
"Absent".<br>
If the output is empty, either
you have long traces and you
didn't get<br>
anything yet (there is no
progress bar for the
synchronization yet). Or<br>
you may have gotten an
exception.<br>
<br>
Can you provide us with your
traces so we can take a closer
look?<br>
<span><font color="#888888"><br>
Geneviève<br>
</font></span>
<div>
<div><br>
<br>
On 14-12-23 02:40 PM,
Matthew Khouzam wrote:<br>
> So you have traces with
network stuff, I would
suggest seeing what<br>
> events are enabled in
your trace. Maybe you are
missing some key events,<br>
> maybe the
synchronization worked and
we're chasing a ghost...<br>
><br>
> I am ccing Genevieve
Bastien, and Masoume
Jabbarifar, the two people
who<br>
> designed and
implemented synchronisation.<br>
><br>
> I am not as much an
expert as I would like to be
in that field.<br>
><br>
> For offsetting though,
it's in tracecompass, the
next version of the<br>
> Eclipse LTTng viewer<br>
><br>
> Here is a link to the
page.<br>
> <a
moz-do-not-send="true"
href="http://projects.eclipse.org/projects/tools.tracecompass"
target="_blank">http://projects.eclipse.org/projects/tools.tracecompass</a><br>
><br>
> On 14-12-23 12:19 AM,
Divya Vyas wrote:<br>
>> Hi,<br>
>><br>
>> Is there any
document which describes how
to synchronize the traces on<br>
>> same machine as
well as different machine (
setting offset also ) .<br>
>><br>
>> I exported the two
trace in experiment and
clicked on synchronize<br>
>> traces . But not
getting anything.<br>
>><br>
>> I followed this
page<br>
>><br>
>> <a
moz-do-not-send="true"
href="http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.linuxtools.lttng.help%2Fdoc%2FTrace-synchronization.html"
target="_blank">http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.linuxtools.lttng.help%2Fdoc%2FTrace-synchronization.html</a><br>
>><br>
>> Thanks,<br>
>> Divya<br>
>><br>
>><br>
>><br>
>> On Mon, Dec 22,
2014 at 11:24 PM, Matthew
Khouzam<br>
>> <<a
moz-do-not-send="true"
href="mailto:matthew.khouzam@ericsson.com"
target="_blank">matthew.khouzam@ericsson.com</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:matthew.khouzam@ericsson.com"
target="_blank">matthew.khouzam@ericsson.com</a>>><br>
>> wrote:<br>
>><br>
>> Sorry, I was a
little hasty in my reply.
You can export traces,<br>
>> but not<br>
>> experiments
yet, this is a feature to
expect soon if people want
it.<br>
>><br>
>><br>
>> On 14-12-22
10:17 AM, Matthew Khouzam
wrote:<br>
>> > Michel has
hit the nail on the head
there.<br>
>> ><br>
>> > I would
just like to add that one
can export an experiment in
trace<br>
>> > compass.
This means that the two
traces are shipped in a zip<br>
>> with the<br>
>> >
synchronization. You can
also apply a constant clock
offset if<br>
>> network<br>
>> > events are
unavailable. If you really
really want to make a CTF<br>
>> trace as<br>
>> > an output,
perhaps look at the python
bound babeltrace?<br>
>> ><br>
>> > BR<br>
>> ><br>
>> > Matthew<br>
>> ><br>
>> ><br>
>> > On
14-12-22 08:07 AM, Michel
Dagenais wrote:<br>
>> >>
Normally, the two traces are
stored separately and they
are<br>
>> "merged"<br>
>> >> at
display time in
TraceCompass. If they were
taken on the same<br>
>> host,<br>
>> >> they
use the same clock and
should be naturally aligned.
If<br>
>> they come<br>
>> >> from
different hosts and you want
very fine symchronization,<br>
>> you need<br>
>> >> some
communication events from
which to synchronize the
traces. TCP<br>
>> >> packet
send and receive events are
typically used. If you want<br>
>> to look<br>
>> >> at two
traces simultaneously, it
normally implies that the
two are<br>
>> >>
related, the two nodes
communicating through the
network.<br>
>> >><br>
>> >><br>
>>
------------------------------------------------------------------------<br>
>> >><br>
>> >>
Hi,<br>
>> >><br>
>> >> Is
there any way to merge the
two CTF traces and see them<br>
>> in one<br>
>> >>
with trace synchronization
?<br>
>> >><br>
>> >>
How it is related to trace
synchronization using
network<br>
>> events ?<br>
>> >><br>
>> >><br>
>> >>
Thanks,<br>
>> >>
Divya<br>
>> >><br>
>> >>
_______________________________________________<br>
>> >>
lttng-dev mailing list<br>
>> >> <a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>><br>
>> >> <a
moz-do-not-send="true"
href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev"
target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >>
_______________________________________________<br>
>> >>
lttng-dev mailing list<br>
>> >> <a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>><br>
>> >> <a
moz-do-not-send="true"
href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev"
target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><br>
>> ><br>
>> >
_______________________________________________<br>
>> > lttng-dev
mailing list<br>
>> > <a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>><br>
>> > <a
moz-do-not-send="true"
href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev"
target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><br>
>><br>
>><br>
>>
_______________________________________________<br>
>> lttng-dev
mailing list<br>
>> <a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:lttng-dev@lists.lttng.org"
target="_blank">lttng-dev@lists.lttng.org</a>><br>
>> <a
moz-do-not-send="true"
href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev"
target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><br>
>><br>
>><br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>