Re: [PATCH] mm/tracking dirty pages: update get_dirty_limits for mmap tracking

[Nate Diller]

On 6/21/06, Nick Piggin <npiggin@xxxxxxx> wrote:
> On Wed, Jun 21, 2006 at 10:01:17AM -0700, Nate Diller wrote:
> > Update write throttling calculations now that we can track and
> > throttle dirty mmap'd pages.  A version of this patch has been tested
> > with iozone:
>
> Your changelog doesn't tell much about the "why" side of things,
> and omits the fact that you have upped the dirty ratio to 80.

hmm, you are right, documenting it in the code comment is not really
enough here, because there are going to be performance corner cases
and such for this patch (as well as the whole tracking dirty patchset)

> >
> > http://namesys.com/intbenchmarks/iozone/06.06.19.tracking.dirty.page-noatime_-B/e3-2.6.16-tr.drt.pgs-rt.40_vs_rt.80.html
> > http://namesys.com/intbenchmarks/iozone/06.06.19.tracking.dirty.page-noatime_-B/r4-2.6.16-tr.drt.pgs-rt.40_vs_rt.80.html
>
> I'm guessing the reason you get all those red numbers when
> iozone files are larger than RAM is because writeout and reclaim
> tend to get worse when there are large amounts of dirty pages
> floating around in memory?

actually, there is a great deal of variation in the test results once
you get into the large I/O part of the test.  also, the fact that we
are tracking mmap'd pages at all changes the preformance.  here are
links which compare the old and new configurations, but with
dirty_pages set to 40 on both:

http://namesys.com/intbenchmarks/iozone/06.06.19.tracking.dirty.page-noatime_-B/e3-2.6.16_vs_tr.drt.pgs-rt.40.html
http://namesys.com/intbenchmarks/iozone/06.06.19.tracking.dirty.page-noatime_-B/r4-2.6.16_vs_tr.drt.pgs-rt.40.html

grev posted the variance as well, but for some reason the link doesn't work.

NATE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/