Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 13 Sep 2002 06:12:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 13 Sep 2002 06:12:27 -0400 Received: from pD952AD04.dip.t-dialin.net ([217.82.173.4]:31979 "EHLO hawkeye.luckynet.adm") by vger.kernel.org with ESMTP id ; Fri, 13 Sep 2002 06:12:27 -0400 Date: Fri, 13 Sep 2002 04:17:15 -0600 (MDT) From: Thunder from the hill X-X-Sender: thunder@hawkeye.luckynet.adm To: Giuliano Pochini cc: riel@conectiva.com.br, Linux Kernel Mailing List , Jim Sibley , Alan Cox , Jesse Pollard Subject: Re: Killing/balancing processes when overcommited In-Reply-To: Message-ID: X-Location: Dorndorf/Steudnitz; Germany MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1072 Lines: 36 Hi, On Fri, 13 Sep 2002, Giuliano Pochini wrote: > > ...the last of the user who has the most processes? > > No, the last one it's likely to be the sysadmin that > logged in to try to fix the situation. Not exactly. if (we run oom) { if (we find a malloc() eater) { kill it; } else if (there's an ->user<- who forked lots of processes) { kill some; } else { kill randomly, based on some table, or whatever...; } } Means we only kill processes if (task->euid) in the second stage. Malloc eaters are likely to be system jobs (such as data servers), so we better don't check the UID then. Thunder -- --./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .- --/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..- .- -/---/--/---/.-./.-./---/.--/.-.-.- --./.-/-.../.-./.././.-../.-.-.- - 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/