linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-mm@kvack.org, linux-nfs@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: TMPFS over NFSv4
Date: Mon, 24 May 2010 15:16:47 +0100	[thread overview]
Message-ID: <AANLkTikjyi1XUzO2VySrXL1evPCRx8YepOAs0I9HCvtp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilMQjZaUom2h_aFgU6WB83IGH-VVKTg-CJD-_ZZ@mail.gmail.com>

hi Hugh.

On Mon, May 24, 2010 at 10:57 AM, Hugh Dickins <hughd@google.com> 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

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2010-05-24 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 13:47 TMPFS over NFSv4 Tharindu Rukshan Bamunuarachchi
2010-05-21 20:55 ` Hugh Dickins
2010-05-24  9:26   ` Tharindu Rukshan Bamunuarachchi
2010-05-24  9:57     ` Hugh Dickins
2010-05-24 10:09       ` Alan Cox
2010-05-24 23:46         ` Hugh Dickins
2010-05-25  9:00           ` Tharindu Rukshan Bamunuarachchi
2010-05-25 16:58             ` Greg KH
2010-05-25 17:00           ` Greg KH
2010-05-24 14:16       ` Tharindu Rukshan Bamunuarachchi [this message]
2010-05-24 10:02     ` Alan Cox
2010-05-24 11:36       ` Tharindu Rukshan Bamunuarachchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikjyi1XUzO2VySrXL1evPCRx8YepOAs0I9HCvtp@mail.gmail.com \
    --to=btharindu@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).