On 9/7/05, Matthew Helsley <[EMAIL PROTECTED]> wrote > I wonder of the I/O usage could be managed by the existing IO > controller in some way. I've never looked at the existing quota hooks so > I don't know how they would help to control IO. Care to elaborate or > point me to some suggestive references?
The quota hooks wouldn't help with I/O tracking, just space tracking/limiting - although for some write-only workloads that might be almost the same thing. > > As I was reading your description I thought of the dentry cache. I > wonder if it might make sense to have a directory classtype with a cache > controller which can classify entries by permission, mode bits, owner > ids, inode, "path" (?), etc. CKRM could then be used to create a class > for directories beneath /usr/share/doc and then a cache controller could > enforce a limit on the cache footprint for that class. I wonder if this > approach could be used to solve the "updatedb" cache pollution problem. > Sounds interesting, although something more automatically tuneable, such as an adaptive caching algorithm like ARC, might be more practical. Paul ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
