Project 2 - Full Cache Simulator

Project description

You will need to extend your trace-driven cache simulator from project 1 to handle different cache configurations, and use it to evaluate the performance of different cache architecture features. Some additional example test outputs for different cache configurations are provided.

Getting Started

Along with files used to make direct submissions to the submit server (submit.jar, .submit), you will find the following new project files:

• Public tests
  • public-block.trace - test cache block sizes
  • public-assoc.trace - test cache associativity
  • public-write.trace - test cache write policy
  • public-instr.trace - test instruction cache
  • spice10000.trace - 1st 10000 accesses in spice.trace
• Expected outputs for public tests
  • public-block.out
  • public-assoc.out
  • public-write.out
  • public-instr.out
  • spice10000-block.out
  • spice10000-assoc.out
  • spice10000-write.out
  • spice10000-instr.out
• runPublic2 - csh script to run public tests

You should also run your simulator using the full application traces (spice.trace, cc.trace, tex.trace) from project 1 to ensure your simulator works properly.

Submission

You may also submit your project directly by executing a Java program on a computer with Java and network access. Use the submit.jar file from the archive p2.zip, To submit, go to the directory containing your project and type the following command:

You will be asked to enter your class account and password, then all files in the directory (and its subdirectories) will be put in a jar file and submitted to the submit server. If your submission is successful you will see the message:

Academic Integrity

The Campus Senate has adopted a policy asking students to include the following statement on each assignment in every course: "I pledge on my honor that I have not given or received any unauthorized assistance on this assignment." Consequently your program is requested to contain this pledge in a comment near the top.

Please carefully read the academic honesty section of the course syllabus. Any evidence of impermissible cooperation on projects, use of disallowed materials or resources, or unauthorized use of computer accounts, will be submitted to the Student Honor Council, which could result in an XF for the course, or suspension or expulsion from the University. Be sure you understand what you are and what you are not permitted to do in regards to academic integrity when it comes to project assignments. These policies apply to all students, and the Student Honor Council does not consider lack of knowledge of the policies to be a defense for violating them. Full information is found in the course syllabus---please review it at this time.