Messages in this thread | | | Subject | RE: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task | Date | Mon, 20 Dec 2004 17:22:34 +0800 | From | "Zou, Nanhai" <> |
| |
> However, based on this and other scattered reports, I'd say it seems > quite likely that token based thrashing control is the culprit. Based > on the cost/benefit, I wonder if we should disable TBTC by default for > 2.6.10, rather than trying to fix it, and try again for 2.6.11? > > Rik? Andrew? > > Also, it would be nice to have a sysctl to *completely* disable TBTC, > that would make testing easier. > > Nick
I have run some stress tests against 2.6.9, 2.6.9 + ignore-swap-token-when-in-trouble.patch and 2.6.10-rc3-mm1 on an Itanium2 with 4G memory.
With 2.6.9 OOM killer will be invoked within a few hours of stress test running.
With 2.6.9 + vmscan-ignore-swap-token-when-in-trouble.patch OOM killer will be invoked around 30 hours.
While 2.6.10-rc3-mm1 seems to be much more stable. At least for the test I was running, it bypassed 48 hours test.
Zou Nan hai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |