Messages in this thread | | | Date | Fri, 18 Mar 2005 09:27:31 +1100 | From | Peter Chubb <> | Subject | Re: vm_dirty_ratio seems a bit large. |
| |
>>>>> "Andrew" == Andrew Morton <akpm@osdl.org> writes:
Andrew> Robin Holt <holt@sgi.com> wrote:
>> One other issue we have is the vm_dirty_ratio and background_ratio >> adjustments are a little coarse with these memory sizes. Since our >> minimum adjustment is 1%, we are adjusting by 40GB on the largest >> configuration from above. The hardware we are shipping today is >> capable of going to far greater amounts of memory, but we don't >> have customers demanding that yet. I would like to plan ahead for >> that and change vm_dirty_ratio from a straight percent into a >> millipercent (thousandth of a percent). Would that type of change >> be acceptable?
Andrew> Oh drat. I think such a change would require a new set of Andrew> /proc entries.
No, you could just extend them to understand fixed point. Keep printing integers as integers, print non-integers with one (or two: will we ever need 0.01% increments?) decimal places.
-- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever* - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |