Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 22 Jul 2002 08:45:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 22 Jul 2002 08:45:42 -0400 Received: from pc2-cwma1-5-cust12.swa.cable.ntl.com ([80.5.121.12]:41710 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 22 Jul 2002 08:45:41 -0400 Subject: Re: [PATCH] strict VM overcommit From: Alan Cox To: Hugh Dickins Cc: Szakacsits Szabolcs , Adrian Bunk , Robert Love , linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Jul 2002 15:01:15 +0100 Message-Id: <1027346475.31787.35.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 659 Lines: 18 On Mon, 2002-07-22 at 13:45, Hugh Dickins wrote: > In strict no-overcommit mode, it should probably decide in advance > whether to embark on swapping off: I think you suggested that > earlier in the thread, that it's acceptable to switch overcommit > mode temporarily to achieve whichever behaviour is desirable? Yes. I have no problem with #swapoff -a swapoff: out of memory #vmctl overcommit 1 #swapoff -a - 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/