From: Tharindu Rukshan Bamunuarachchi Subject: Re: TMPFS over NFSv4 Date: Mon, 24 May 2010 15:16:47 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-mm@kvack.org, linux-nfs@vger.kernel.org, Alan Cox To: Hugh Dickins Return-path: Received: from mail-gw0-f46.google.com ([74.125.83.46]:49753 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757006Ab0EXORT (ORCPT ); Mon, 24 May 2010 10:17:19 -0400 Received: by gwaa20 with SMTP id a20so1499859gwa.19 for ; Mon, 24 May 2010 07:17:17 -0700 (PDT) In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: hi Hugh. On Mon, May 24, 2010 at 10:57 AM, Hugh Dickins wrote: > On Mon, May 24, 2010 at 2:26 AM, Tharindu Rukshan Bamunuarachchi > > 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. > I will just add it by hand. > > > So what you see fits with what Alan was fixing. > Yes, of courese. BTW, that was typo and it should be overcommit_memory. I have done testing in our test severs and "2 > overcommit_memory" triggers the issue. OTOH, I have reported the issue Novell. Hope they will apply necessary patch in next release. > Hugh > Thankx a lot/ __ tharindu