<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 20, 2013, at 10:14 PM, Glenn Elliott <<a href="mailto:gelliott@cs.unc.edu">gelliott@cs.unc.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I’m afraid not. This is one reason why it’s not found in the LITMUS^RT github repositories, but rather in B. Brandenburg’s.</blockquote><div><br></div><div>This is an unsupported code dump. I'm unfortunately unable to provide tech support for this code due to time constraints. However, as Glenn pointed out, it's actually not that hard to use. If you want to visualize schedules, you'll have to have the Asymptote package installed.</div><br><blockquote type="cite"><div><div><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Suppose you want to write code that finds the response time (release time minus completion time) for every job. Each job can be uniquely identified by a pid/job number pair. These fields are found in the st_trace_header struct, which is a part of every sched_trace event. st_release_data has the job release time. st_completion_data has the completion time. Use the st_trace_header in each release/completion to match release events with completion events.</div></div></div></blockquote><br></div><div>Just FYI: there's a tool called st_job_stats in the repo that extracts response-time distributions (among other stats).</div><div><br></div><div>Regards,</div><div>Björn</div><div><br></div></body></html>