<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 30, 2018 at 5:38 PM, Russell Haley <span dir="ltr"><<a href="mailto:russ.haley@gmail.com" target="_blank">russ.haley@gmail.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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Apr 30, 2018 at 3:05 AM, Sebastian Huber <span dir="ltr"><<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-<wbr>brains.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Vidushi,<span><br>
<br>
On 30/04/18 09:15, Vidushi Vashishth wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello!<br>
<br>
I am Vidushi Vashishth, and I have been selected for the Google Summer of Code'18 program. I look forward to a productive and enriching summer with the RTEMS community.<br>
</blockquote>
<br></span>
I am looking forward to get some new insights into a network stack performance issue with 10Gbit/s Ethernet on a QorIQ T4240 with your tracing support.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I will be working on enhancement of the tracing system of RTEMS, under the guidance of mentors: Gedare Bloom, Chris Johns and Sebastian Huber. The main objectives of my project are threefold:<br>
<br>
1) Combine the Common Trace Format with the functionality of the Trace Linker. I will be working with barectf and rtems-tld in this regard.<br>
2) Coming up with a synchronisation and transport mechanism to send trace records to the host machine.<br>
3) Investigate the importance of live tracing functionality and addition of kernel level tracing. I will design both possibilities and decide which one to work on by the end of phase 1 of my evaluation.<br>
</blockquote>
<br></span>
I work currently on a new low level infrastructure to support gathering of thread (create, delete, terminate, switch) and interrupt (entry, exit) events. Similar to the capture engine, but with less overhead. I would like to be able to gather at least 200000 events per second per processor (24 on the QorIQ T4240). This results in about 80MiB/s of data so that I can transfer it easily via a 1Gbit/s Ethernet interface.<br>
<br>
I don't know how to setup the CTF infrastructure to display this data. I hope that you can help me here.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The wiki page for my project is: <a href="https://devel.rtems.org/wiki/GSoC/2018/EnhancementRuntimeTracing" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/G<wbr>SoC/2018/EnhancementRuntimeTra<wbr>cing</a><br>
<br>
I will be documenting the progress of my project on my blog: <a href="https://vidushivashishth.github.io/" rel="noreferrer" target="_blank">https://vidushivashishth.githu<wbr>b.io/</a><br>
<br>
Both of these sources are empty right now but will be modified with relevant information over the course of this summer.<br>
</blockquote>
<br></span>
I would prefer to use the ticket system as much as possible for this project.<br></blockquote><div><br></div></span><div>Should Udit also be using the ticket system? Or is the ticket system deemed less important for his project? </div></div></div></div></blockquote><div><br></div><div>As much as possible, all students should. I know for the POSIX improvements project, I set it up as a "meta project" where adding a method or set of methods is a single ticket.</div><div><br></div><div>There is a tag for "SoC" projects.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The main audience for the runtime tracing are the RTEMS users. A key issue is to provide adequate documentation so that it is easy to use. If you need this tracing then you probably have a nasty application issue and no time to struggle with setting up things with a project deadline looming. Where should this documentation go? A new chapter in the User Manual<br>
<br>
<a href="https://docs.rtems.org/branches/master/user/index.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branche<wbr>s/master/user/index.html</a><br>
<br>
?<br>
<br>
-- <br>
Sebastian Huber, embedded brains GmbH<br>
<br>
Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>
Phone : +49 89 189 47 41-16<br>
Fax : +49 89 189 47 41-09<br>
E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brain<wbr>s.de</a><br>
PGP : Public key available on request.<br>
<br>
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
<br>
______________________________<wbr>_________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman<wbr>/listinfo/users</a></blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/users</a><br></blockquote></div><br></div></div>