From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from max.fys.ruu.nl (max.fys.ruu.nl [131.211.32.73]) by kvack.org (8.8.7/8.8.7) with ESMTP id PAA18163 for ; Mon, 23 Mar 1998 15:40:24 -0500 Date: Mon, 23 Mar 1998 21:24:21 +0100 (MET) From: Rik van Riel Reply-To: Rik van Riel Subject: vmscan.c loop fix. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Linus Torvalds Cc: linux-mm List-ID: Hi Linus, I think the 'proper' fix for swapout loops would be to limit the amount of CPU used by kswapd (to 50%?). We could do that by: - having kswapd measure it's own CPU usage (over a 30 second period?) - exiting after 3 jiffies (32 Alpha) max when it's usage is above quota and setting a hard_next_swap_jiffies to jiffies + 3 Of course, this has the disadvantage that kswapd can't keep up with allocation festivities :-( What do you think? Rik. +-------------------------------------------+--------------------------+ | Linux: - LinuxHQ MM-patches page | Scouting webmaster | | - kswapd ask-him & complain-to guy | Vries cubscout leader | | http://www.fys.ruu.nl/~riel/ | | +-------------------------------------------+--------------------------+