On Wed, 27 Dec 2006, Chen, Kenneth W wrote:
> >
> > Running the test code, git bisect points its finger at this commit.
> > Reverting
> > this commit on top of 2.6.20-rc2 doesn't trigger the bug from the test code.
> >
> > [PATCH] mm: balance dirty pages
> >
> > Now that we can detect writers of shared mappings, throttle them.
> > Avoids OOM
> > by surprise.
>
> Oh, never mind :-( I just didn't create enough write out pressure when
> test this. I just saw bug got triggered on a kernel I previously thought
> was OK.
Btw, this is an important point - people have long felt that the new page
balancing in 2.6.19 was to blame, but you've just confirmed the long-held
suspicion (at least by me) that it's not actually a new bug at all, it's
just that the dirty page balancing causes writeback to happen _earlier_,
and thus is better able to _show_ a bug that we've likely had for a long
long time.
Linus
-
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/
