Project 6 - File System

More documents

Recommendations

Info

<strong>Project</strong> 6 Considerations Correctness Disk controllers will reorder requests Need to handle crashes smoothly: Ctrl+C: disk should be in a consistent state. Disk crashes: don’t issue any more requests to it. We will test failure conditions: extern double crash_rate; extern double failure_rate; extern double reordering_rate;
<strong>Project</strong> 6 Considerations Efficiency Start with simple data structures (e.g. a single inode per block). Focus on correctness. Breath-taking performance won’t help if your system doesn’t work as specified. § Premature optimization is the root of all evil (Knuth) Do fancy things later § Also known as, “I don’t care that your Ferarri is fast if it only does left-hand turns.”
Page 1 and 2: Project 6 Project 6 File System Sea
Page 3 and 4: Project 6 Project Scope 1 Project S
Page 5 and 6: Project 6 Project Scope Our propose
Page 7 and 8: Project 6 Project Scope How does th
Page 9 and 10: Project 6 Implementation Details Cr
Page 11 and 12: Project 6 Implementation Details Th
Page 19 and 20: Project 6 Filesystem Structure A pi
Page 21 and 22: Project 6 Filesystem Structure The
Page 23 and 24: Project 6 Filesystem Structure File
Page 25 and 26: Project 6 Concurrent Access 1 Proje
Page 27 and 28: Project 6 Concurrent Access UNIX re
Page 29 and 30: Project 6 Concurrent Access Alterna
Page 31 and 32: Project 6 Concurrent Access Deletio
Page 33: Project 6 Considerations Keep inter
Page 37 and 38: Project 6 Considerations Testing Us
Page 39: Project 6 Considerations Concluding

Project 6 - File System

Create successful ePaper yourself

Delete template?

Save as template?