<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mc2-scripts-and-benchmarks.git/baseline/tacleNames.txt, branch rtas21-ae</title>
<subtitle>Benchmarks and execution scripts for testing spatial isolation and SMT interference in MC^2</subtitle>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/mc2-scripts-and-benchmarks.git/'/>
<entry>
<title>Add pair benchmarking and isolation specification into run_bench.sh</title>
<updated>2020-10-22T04:08:12+00:00</updated>
<author>
<name>Joshua Bakita</name>
<email>jbakita@cs.unc.edu</email>
</author>
<published>2020-10-22T04:08:12+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/mc2-scripts-and-benchmarks.git/commit/?id=3b0aa125061b362b23ecf66afe8319e3a268c874'/>
<id>3b0aa125061b362b23ecf66afe8319e3a268c874</id>
<content type='text'>
This allows `run_bench.sh` to replace all previous general paired
benchmarking scripts. See `run_everything.sh` for an example of how
to use the new script.

This also fixes two critical bugs present in the old scripts:
1. The cpus_list was incorrectly set for resctrl when running
   synchronous pair timing with L2+L3 isolation (i). Each write
   to that file replaces the previous contents, and it was previously
   written once for each core. This prevented the entire 1st core
   from using any L3 cache.
2. The competing task list was indexed improperly in the asynchronous
   pair timing script. This caused the competing task to always be
   identical to the task being profiled.
These issues combine to imply that in the rejected RTSS'20 paper:
- All Level-C SMT timing data is suspect
- Level-A and -B SMT timing data with L2+L3 isolation (i) is
  wildly optimistic
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows `run_bench.sh` to replace all previous general paired
benchmarking scripts. See `run_everything.sh` for an example of how
to use the new script.

This also fixes two critical bugs present in the old scripts:
1. The cpus_list was incorrectly set for resctrl when running
   synchronous pair timing with L2+L3 isolation (i). Each write
   to that file replaces the previous contents, and it was previously
   written once for each core. This prevented the entire 1st core
   from using any L3 cache.
2. The competing task list was indexed improperly in the asynchronous
   pair timing script. This caused the competing task to always be
   identical to the task being profiled.
These issues combine to imply that in the rejected RTSS'20 paper:
- All Level-C SMT timing data is suspect
- Level-A and -B SMT timing data with L2+L3 isolation (i) is
  wildly optimistic
</pre>
</div>
</content>
</entry>
<entry>
<title>Reorganize and commit all the modified TACLeBench code and run scripts</title>
<updated>2019-10-07T23:13:39+00:00</updated>
<author>
<name>Joshua Bakita</name>
<email>bakitajoshua@gmail.com</email>
</author>
<published>2019-10-07T23:13:39+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/mc2-scripts-and-benchmarks.git/commit/?id=386b7d3366f1359a265da207a9cafa3edf553b64'/>
<id>386b7d3366f1359a265da207a9cafa3edf553b64</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
