Third Paper Survey
Sign in to Google to save your progress. Learn more
Please rate the following papers
Keep this paper -- I really liked it.
Keep this paper -- I didn't particularly like it but it was educational.
I'm pretty indifferent about this paper.
I don't think you should include this paper next time.
Herlihy: Transactional Memory: Architectural Support for Lock-Free Data Structures
Damron: Hybrid transactional memory
Clements: The Scalable Communtativity Rule: Designing Scalable Software
David: Everything You Always Wanted to Know about Synchronization but were Afraid to Ask
Lamport: The Part time Parliament
Ongara: In Search of an Understandable Consensus Algorithm
Rinard: Enhancing Server Availability and Security Through Failure-Oblivious Computing
Qin: Rx: Treating Bugs as Software Allergies -- A Safe way to Survive Software Failures
Engler: Bugs as Deviant Behavior: A General Approach to Inferring Errors in Systems Code
Wang: Towards Optimization-Safe Systems
Zeldovich: Making information flow explicit in HiStar
Tice: Enforcing Forward-Edge Control-Flow Integrity in GCC and LLVM 
Levis: Experiences from a Decade of TinyOS Development
Elphinstone: From L3 to seL4: What Have We Learnt in 20 Years of L4 Microkernels?
Lampson: Hinds for System Design
Clear selection
Have the reading guidelines/tips been useful? *
If you answered no to the question above, what could I do to make them more useful?
What can we do to make class discussion more valuable? *
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report