Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262539AbVAPQY6 (ORCPT ); Sun, 16 Jan 2005 11:24:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262538AbVAPQY6 (ORCPT ); Sun, 16 Jan 2005 11:24:58 -0500 Received: from mail-in-05.arcor-online.net ([151.189.21.45]:49298 "EHLO mail-in-05.arcor-online.net") by vger.kernel.org with ESMTP id S262540AbVAPQXb (ORCPT ); Sun, 16 Jan 2005 11:23:31 -0500 From: Bodo Eggert <7eggert@gmx.de> Subject: Re: User space out of memory approach To: Edjard Souza Mota , Alan Cox , Ilias Biris , Linux Kernel Mailing List Reply-To: 7eggert@gmx.de Date: Sun, 16 Jan 2005 17:28:26 +0100 References: User-Agent: KNode/0.7.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1113 Lines: 17 Edjard Souza Mota wrote: > What do you think about the point we are trying to make, i.e., moving the > ranking of PIDs to be killed to user space? If my system needs the OOM killer, it's usurally unresponsive to most userspace applications. A normal daemon would be swapped out before the runaway dhcpd grows larger than the web cache. It would have to be a mlocked RT task started from early userspace. It would be difficult to set up (unless you upgrade your distro), and almost nobody will feel like tweaking it to take the benefit (OOM == -ECANNOTHAPPEN). What about creating a linked list of (stackable) algorhithms which can be extended by loading modules and resorted using {proc,sys}fs? It will avoid the extra process, the extra CPU time (and task switches) to frequently update the list and I think it will decrease the typical amount of used memory, too. - 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/