Rob can der Heij wrote: >Right now my biggest problem is kswapd that wants a wakeup call every >second, and I would be interesting to hear if someone can explain why it >is a smart way to implement memory management like this. If no work was >done since the previous call of kswapd, it should be possible to predict >what needs to be done.
What kernel are you talking about? Memory management has changed drastically between 2.4.7 and 2.4.17/19, and the current 2.5 stuff is drastically different again. This once-a-second wakeup for kswapd looks like an artifact of the 2.4.7-period MM design, even 2.4.17 doesn't have that any more as far as I can see. >Once this is gone, the 5-second interval for kswapd is the next one to >address. I'm not sure what you are talking about here ... Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
