Suggestion: to improve file system performance, first document the bad behavior in detail.
Begin with examples of traces/logs of disk accesses associated with file system operations. Include scenarios (one hopes reproducible ones) to provoke bad behavior. Are reads worse than writes? Sequential vs. random? Interleaved r/w on one file? On more than one file simultaneously? Examples from other O/S which are better or worse? Without this very detailed data it's all noise. Being able to get good traces & correlate them with OS activity shows at least some competence dealing with OS internals. geoff steckel
