From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail190.messagelabs.com (mail190.messagelabs.com [216.82.249.51]) by kanga.kvack.org (Postfix) with ESMTP id 94DD56B01B0 for ; Mon, 24 May 2010 06:01:45 -0400 (EDT) Date: Mon, 24 May 2010 11:09:03 +0100 From: Alan Cox Subject: Re: TMPFS over NFSv4 Message-ID: <20100524110903.72524853@lxorguk.ukuu.org.uk> In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Hugh Dickins Cc: Tharindu Rukshan Bamunuarachchi , linux-mm@kvack.org, linux-nfs@vger.kernel.org List-ID: On Mon, 24 May 2010 02:57:30 -0700 Hugh Dickins wrote: > On Mon, May 24, 2010 at 2:26 AM, Tharindu Rukshan Bamunuarachchi > wrote: > > thankx a lot Hugh ... I will try this out ... (bit harder patch > > already patched SLES kernel :-p ) .... > > If patch conflicts are a problem, you really only need to put in the > two-liner patch to mm/mmap.c: Alan was seeking perfection in > the rest of the patch, but you can get away without it. > > > > > BTW, what does Alan means by "strict overcommit" ? > > Ah, that phrase, yes, it's a nonsense, but many of us do say it by mistake. > Alan meant to say "strict no-overcommit". No I always meant to say 'strict overcommit'. It avoids excess negatives and "no noovercommit" discussions. I guess 'strict overcommit control' would have been clearer 8) Alan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org