Hi, Thanks for your comments. I'm sorry for my late reply. Bill Davidsen wrote: >> Then, what do you think of the following idea? >> >> (4) add `dirty_start_writeback_ratio' as percentage of memory, >> at which a generator of dirty pages itself starts writeback >> (that is, non-blocking ratio). >> >> In this way, `dirty_ratio' is used as the blocking ratio, so we don't >> need to modify the sysctl.conf etc. I think it's easier to understand >> for administrators of systems, because the interface is similar as >> `dirty_background_ratio' and`dirty_ratio.' >> > It sounds good to me, just be sure behavior is sane for for both > blocking less than start_writeback and vice versa.
Then I'm going to post the new patchset. In my new patchset, if dirty_ratio < dirty_start_writeback_ratio, dirty_start_writeback_ratio is just regarded as the same value as dirty_ratio, and then the kernel behaves similarly as the current kernel. Regards, -- Tomoki Sekiyama Hitachi, Ltd., Systems Development Laboratory - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
