On Fri, Oct 23, 2009 at 06:58:10PM +0200, Karol Lewandowski wrote: > On Thu, Oct 22, 2009 at 03:22:31PM +0100, Mel Gorman wrote: > > Test 3: If you are getting allocation failures, try with the following patch > > > > 3/5 vmscan: Force kswapd to take notice faster when high-order watermarks > > are being hit
> No, problem doesn't go away with these patches (1+2+3). However, from > my testing this particular patch makes it way, way harder to trigger > allocation failures (but these are still present). > > This bothers me - should I test following patches with or without > above patch? This patch makes bug harder to find, IMVHO it doesn't > fix the real problem. .. > Test 4: If you are still getting failures, apply the following > 4/5 page allocator: Pre-emptively wake kswapd when high-order watermarks are > hit Ok, I've tested patches 1+2+4 and bug, while very hard to trigger, is still present. I'll test complete 1-4 patchset as time permits. Thanks. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
