> > > Then, how to deal with this issue in 2.3, leave it here? or make an > > > incomplete fix like I do above? > > > > I think it is better to leave it here for 2.3. With a patch like this > > one, we improve in one load and we got worse in a different load > > (depens a lot in the ratio of dirtying memory vs disk). I have no > > data which load is more common, so I prefer to be conservative so late > > in the cycle. What do you think? > > I agree, it's too late in the release cycle for such a change. > > Kevin
That's OK.
