Yes, it is for dirty cache limiting on a per-osc basis. There is also /proc/fs/lustre/llite/*/max_cached_mb that regulates how much cached data per client you can have. (default is 3/4 of RAM)
On Apr 3, 2009, at 2:52 PM, Lundgren, Andrew wrote: > The parameter is called dirty, is that write cache, or is it read- > write? > >> >> Current Lustre does not cache on OSTs at all. All IO is direct. >> Future Lustre releases will provide an OST cache. >> >> For now, you can increase the amount of data cached on clients, which >> might help a little. Client caching is set with >> /proc/fs/lustre/osc/*/max_dirty_mb. >> > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss@lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss