From: Gleb Natapov <gleb@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH][RFC] add MAP_UNLOCKED mmap flag
Date: Tue, 6 Oct 2009 12:21:36 +0200 [thread overview]
Message-ID: <20091006102136.GH9832@redhat.com> (raw)
In-Reply-To: <20091006190938.126F.A69D9226@jp.fujitsu.com>
On Tue, Oct 06, 2009 at 07:11:06PM +0900, KOSAKI Motohiro wrote:
> Hi
>
> > 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. 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>
>
> Why don't you use explicit munlock()?
Because mmap will fail before I'll have a chance to run munlock on it.
Actually when I run my process inside memory limited container host dies
(I suppose trashing, but haven't checked).
> Plus, Can you please elabrate which workload nedd this feature?
>
I wanted to run kvm with qemu process locked in memory, but guest memory
unlocked. And guest memory is bigger then host memory in the case I am
testing. I found out that it is impossible currently.
--
Gleb.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH][RFC] add MAP_UNLOCKED mmap flag
Date: Tue, 6 Oct 2009 12:21:36 +0200 [thread overview]
Message-ID: <20091006102136.GH9832@redhat.com> (raw)
In-Reply-To: <20091006190938.126F.A69D9226@jp.fujitsu.com>
On Tue, Oct 06, 2009 at 07:11:06PM +0900, KOSAKI Motohiro wrote:
> Hi
>
> > 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. 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>
>
> Why don't you use explicit munlock()?
Because mmap will fail before I'll have a chance to run munlock on it.
Actually when I run my process inside memory limited container host dies
(I suppose trashing, but haven't checked).
> Plus, Can you please elabrate which workload nedd this feature?
>
I wanted to run kvm with qemu process locked in memory, but guest memory
unlocked. And guest memory is bigger then host memory in the case I am
testing. I found out that it is impossible currently.
--
Gleb.
next prev parent reply other threads:[~2009-10-06 10:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 9:51 [PATCH][RFC] add MAP_UNLOCKED mmap flag Gleb Natapov
2009-10-06 9:51 ` Gleb Natapov
2009-10-06 10:09 ` Frederik Deweerdt
2009-10-06 10:09 ` Frederik Deweerdt
2009-10-06 10:11 ` KOSAKI Motohiro
2009-10-06 10:11 ` KOSAKI Motohiro
2009-10-06 10:21 ` Gleb Natapov [this message]
2009-10-06 10:21 ` Gleb Natapov
2009-10-06 10:27 ` KOSAKI Motohiro
2009-10-06 10:27 ` KOSAKI Motohiro
2009-10-06 10:33 ` Gleb Natapov
2009-10-06 10:33 ` Gleb Natapov
2009-10-06 12:10 ` KOSAKI Motohiro
2009-10-06 12:10 ` KOSAKI Motohiro
2009-10-06 12:16 ` Gleb Natapov
2009-10-06 12:16 ` Gleb Natapov
2009-10-06 13:50 ` Peter Zijlstra
2009-10-06 13:50 ` Peter Zijlstra
2009-10-06 14:06 ` Gleb Natapov
2009-10-06 14:06 ` Gleb Natapov
2009-10-07 18:50 ` Olivier Galibert
2009-10-07 18:50 ` Olivier Galibert
2009-10-07 18:59 ` Gleb Natapov
2009-10-07 18:59 ` Gleb Natapov
2009-10-07 20:10 ` Olivier Galibert
2009-10-07 20:10 ` Olivier Galibert
2009-10-07 20:47 ` Gleb Natapov
2009-10-07 20:47 ` Gleb Natapov
2009-10-06 10:49 ` Arnd Bergmann
2009-10-06 11:00 ` Gleb Natapov
2009-10-06 11:00 ` 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=20091006102136.GH9832@redhat.com \
--to=gleb@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.