Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933633AbWKWMhG (ORCPT ); Thu, 23 Nov 2006 07:37:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933631AbWKWMhF (ORCPT ); Thu, 23 Nov 2006 07:37:05 -0500 Received: from smtp3.orange.fr ([193.252.22.28]:6236 "EHLO smtp-msa-out03.orange.fr") by vger.kernel.org with ESMTP id S933633AbWKWMg4 (ORCPT ); Thu, 23 Nov 2006 07:36:56 -0500 X-ME-UUID: 20061123123655651.9EFD71C003D2@mwinf0303.orange.fr Subject: Re: coping with swap-exhaustion in 2.4.33-4 From: Xavier Bestel To: Yakov Lerner Cc: Kernel In-Reply-To: References: Content-Type: text/plain Date: Thu, 23 Nov 2006 13:36:52 +0100 Message-Id: <1164285412.13074.131.camel@frg-rhel40-em64t-03> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-27) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 661 Lines: 16 On Thu, 2006-11-23 at 14:30 +0200, Yakov Lerner wrote: > Where can I read anything about how kernel is supposed to > react to the 'swap-full' condition ? We have troubles on the > production machine which routinely arrives to the swap-full state > no matter how I increase the swap, because user proceses multi-fork > and then want to allocate a lot of virtual memory. Did you disable memory overcommit ? Xav - 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/