Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 18 Jul 2002 18:27:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 18 Jul 2002 18:27:49 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:23278 "EHLO hermes.mvista.com") by vger.kernel.org with ESMTP id ; Thu, 18 Jul 2002 18:27:47 -0400 Subject: Re: [PATCH] strict VM overcommit for stock 2.4 From: Robert Love To: Rik van Riel Cc: Szakacsits Szabolcs , linux-mm@kvack.org, linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 18 Jul 2002 15:30:22 -0700 Message-Id: <1027031422.1555.161.camel@sinai> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 759 Lines: 21 On Thu, 2002-07-18 at 15:24, Rik van Riel wrote: > I see no reason to not merge this (useful) part. Not only > is it useful on its own, it's also a necessary ingredient > of whatever "complete solution" to control per-user resource > limits. I am glad we agree here - resource limits and strict overcommit are two separate solutions to various problems. Some they solve individually, others they solve together. I may use one, the other, both, or neither. A clean abstract solution allows this. Robert Love - 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/