[lkml]   [2009]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bug #12809] iozone regression with 2.6.29-rc6

On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.28. Please verify if it still should be listed and let me know
> (either way).
> Bug-Entry :
> Subject : iozone regression with 2.6.29-rc6
> Submitter : Lin Ming <>
> Date : 2009-02-27 9:13 (16 days old)
> First-Bad-Commit:;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References :
> Handled-By : Wu Fengguang <>

I suspect that I should just raise the default dirty limits. Wu reported
that it fixed the regression, and while he picked some rather high
percentages, I think we could certainly raise the rather aggressive
default ones.

After all, those default percentages were picked (a) with the old dirty
logic and (b) largely at random and (c) designed to be aggressive. In
particular, that (a) means that having fixed some of the dirty accounting,
maybe the real bug is now that it was always too aggressive, just hidden
by an accounting issue.

If we raised the default ratio from 5/10 to 10/20, what happens to the
iozone regression?


 \ /
  Last update: 2009-03-15 01:35    [W:0.301 / U:0.348 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site