Messages in this thread | | | Date | Mon, 20 Dec 2004 18:44:49 +1100 | From | Nick Piggin <> | Subject | Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task |
| |
Andrew Morton wrote: > Voluspa <lista4@comhem.se> wrote: > >>Would be nice though if someone else could verify... > > > Well I'd love to, but afaik the only workloads which we currently know of > involve complex userspace apps which I have no experience running. > > Did anyone come up with a simple step-by-step procedure for reproducing the > problem? It would be good if someone could do this, because I don't think > we understand the root cause yet? >
I admit to generally being in the same boat as you with respect to running complex userspace apps.
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 - 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/
| |