From: Chris Wright <chrisw@sous-sol.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH v5] add MAP_UNLOCKED mmap flag
Date: Wed, 13 Jan 2010 09:31:52 -0800 [thread overview]
Message-ID: <20100113173152.GA2666@sequoia.sous-sol.org> (raw)
In-Reply-To: <20100113093119.GT7549@redhat.com>
* Gleb Natapov (gleb@redhat.com) wrote:
> If application does mlockall(MCL_FUTURE) it is no longer possible to mmap
> file bigger than main memory or allocate big area of anonymous memory
> in a thread safe manner. Sometimes it is desirable to lock everything
> related to program execution into memory, but still be able to mmap
> big file or allocate huge amount of memory and allow OS to swap them on
> demand. MAP_UNLOCKED allows to do that.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
Looks good to me.
Acked-by: Chris Wright <chrisw@sous-sol.org>
thanks,
-chris
--
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>
next prev parent reply other threads:[~2010-01-13 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:31 Gleb Natapov
2010-01-13 14:36 ` Américo Wang
2010-01-13 17:31 ` Chris Wright [this message]
2010-01-14 0:31 ` KOSAKI Motohiro
2010-01-14 6:50 ` Gleb Natapov
2010-01-14 7:02 ` KOSAKI Motohiro
2010-01-14 7:22 ` Gleb Natapov
2010-01-14 7:30 ` KOSAKI Motohiro
2010-01-14 8:01 ` Gleb Natapov
2010-01-14 8:17 ` KOSAKI Motohiro
2010-01-14 10:22 ` Gleb Natapov
2010-01-14 19:30 ` Andrew C. Morrow
2010-01-18 3:23 ` KOSAKI Motohiro
2010-01-18 13:40 ` Gleb Natapov
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=20100113173152.GA2666@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.org \
--cc=gleb@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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