[LITMUS^RT] Trace unit ?

[Sanjib Das]

Hi,
Thank you very much. But, For each experiment with PFAIR scrip returns 3
couples of  CSVs and PDFs. Where PDFs are labeled as CXS_task_Avg_Avg,
CXS_task_Min_Min, CXS_task_Min_Avg, CXS_task_Var_Avg, CXS_task_Max_Max,
CXS_task_Max_Avg, and there is not label on the generated graph .

Can you please help me in this particulate case  ?

Thanks in advance
Sanjib




On Thu, Jun 19, 2014 at 1:05 PM, Björn Brandenburg <bbb at mpi-sws.org> wrote:

>
> On 19 Jun 2014, at 12:03, Sanjib Das <cnt.sanjib at googlemail.com> wrote:
>
> • RELEASE_LATENCY: Used to measure the difference between when a
> timer should have fired, and when it actually did fire. In contrast to all
> other time stamps, this overhead is directly measured in
> nanoseconds(**********and not in processor cycles as the other
> overheads*********).
>
>
> Except RELEASE_LATENCY, are all the others measured in milliseconds ?
>
> Or how can I determine that .
>
>
> See above. Feather-Trace reports processor cycles.
>
> - Björn
>
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20140619/7f631495/attachment.html>