Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756601Ab0BGW6H (ORCPT ); Sun, 7 Feb 2010 17:58:07 -0500 Received: from smtp-out003.kontent.com ([81.88.40.217]:46559 "EHLO smtp-out003.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755970Ab0BGW6F (ORCPT ); Sun, 7 Feb 2010 17:58:05 -0500 From: Oliver Neukum To: David Rientjes Subject: Re: Improving OOM killer Date: Fri, 5 Feb 2010 08:35:30 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.33-rc6-0.1-default; KDE/4.3.1; x86_64; ; ) Cc: Jiri Kosina , Lubos Lunak , Balbir Singh , Rik van Riel , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , KOSAKI Motohiro , Nick Piggin References: <201002012302.37380.l.lunak@suse.cz> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002050835.30550.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 999 Lines: 22 Am Donnerstag, 4. Februar 2010 22:39:08 schrieb David Rientjes: > > If we really want kernel to detect forkbombs (*), we'd have to establish > > completely separate infrastructure for that (with its own knobs for tuning > > and possibilities of disabling it completely). > > > > That's what we're trying to do, we can look at the shear number of > children that the parent has forked and check for it to be over a certain > "forkbombing threshold" (which, yes, can be tuned from userspace), the > uptime of those children, their resident set size, etc., to attempt to > find a sane heuristic that penalizes them. Wouldn't it be saner to have a selection by user, so that users that are over the overcommit limit are targeted? Regards Oliver -- 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/