Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751697AbVIZRdd (ORCPT ); Mon, 26 Sep 2005 13:33:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751699AbVIZRdd (ORCPT ); Mon, 26 Sep 2005 13:33:33 -0400 Received: from [212.76.86.33] ([212.76.86.33]:4612 "EHLO raad.intranet") by vger.kernel.org with ESMTP id S1751694AbVIZRdc (ORCPT ); Mon, 26 Sep 2005 13:33:32 -0400 From: Al Boldi To: Alan Cox Subject: Re: Resource limits Date: Mon, 26 Sep 2005 20:32:12 +0300 User-Agent: KMail/1.5 Cc: linux-kernel@vger.kernel.org References: <1127754691.27757.26.camel@localhost.localdomain> In-Reply-To: <1127754691.27757.26.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509262032.12081.a1426z@gawab.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 806 Lines: 25 Alan Cox wrote: > On Llu, 2005-09-26 at 09:44 -0500, Roger Heflin wrote: > > While talking about limits, one of my customers report that if > > they set "ulimit -d" to be say 8GB, and then a program goes and > > The kernel doesn't yet support rlimit64() - glibc does but it emulates > it best effort. Thats a good intro project for someone > > > It would seem that the best thing to do would be to abort on > > allocates that will by themselves exceed the limit. > > 2.6 supports "no overcommit" modes. By name only. see "Kswapd flaw" thread. Thanks! -- Al - 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/