Skip to contentSkip to conversation

2.6.10-rc3: kswapd eats CPU on start of memory-eating task

DISCUSSION Voluspa 2 participants 2 messages Dec 20, 2004 – Dec 21, 2004

lore
Share & tools
lore

Voluspa

author
#0 lore raw
Quoted 4 lines · Con Kolivas
Quoted 4 lines

Logistically what makes sense is if a timeout of 0 is used as a test that completely disables it (avoids another sysctl too). In time for 2.6.10 we should disable it by default until the regressions are better understood. Tuning it into a useful "on" position can happen later and

I

Quoted 3 lines
Quoted 1 line

suspect requires more code.

This patch should have the desired effect.

Yes, it sure has. And with that I mean, YES. My testcase shows no freezes now, and it has the same swapping time as 2.6.8.1-bk2.

Thanks Con,
Mats Johannesson

#1 lore raw
Quoted 4 lines · Voluspa
Quoted 1 line

This patch should have the desired effect.

Yes, it sure has. And with that I mean, YES. My testcase shows no freezes now, and it has the same swapping time as 2.6.8.1-bk2.

Confirmed.

On 2.6.10-rc3 with Con's patch, when I run the memory eater, there is a high kswapd CPU load for about 10 seconds, then things are OK. The screen never freezes at that time or at any other moment.

When I add vm-pageout-throttling.patch from -mm, the CPU load in the beginning is somewhat less constant but remains there.

While it would be nice to fix the high CPU load, the system is usable as it is.

Signature · 1 line
Yours, Mikhail Ramendik