From: Peter Zijlstra <peterz@infradead.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
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, 06 Oct 2009 15:50:03 +0200 [thread overview]
Message-ID: <1254837003.21044.283.camel@laptop> (raw)
In-Reply-To: <20091006121603.GK9832@redhat.com>
On Tue, 2009-10-06 at 14:16 +0200, Gleb Natapov wrote:
> > No, I only think your case doesn't fit MC_FUTURE.
> > I haven't find any real benefit in this patch.
> I did. It allows me to achieve something I can't now. Steps you provide
> just don't fit my needs. I need all memory areas (current and feature) to be
> locked except one. Very big one. You propose to lock memory at some
> arbitrary point and from that point on all newly mapped memory areas will
> be unlocked. Don't you see it is different?
While true, it does demonstrates very sloppy programming. The proper fix
is to rework qemu to mlock what is needed.
I'm not sure encouraging mlockall() usage is a good thing. When using
resource locks one had better know what he's doing. mlockall() doesn't
promote caution.
--
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:[~2009-10-06 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 9:51 Gleb Natapov
2009-10-06 10:09 ` Frederik Deweerdt
2009-10-06 10:11 ` KOSAKI Motohiro
2009-10-06 10:21 ` Gleb Natapov
2009-10-06 10:27 ` KOSAKI Motohiro
2009-10-06 10:33 ` Gleb Natapov
2009-10-06 12:10 ` KOSAKI Motohiro
2009-10-06 12:16 ` Gleb Natapov
2009-10-06 13:50 ` Peter Zijlstra [this message]
2009-10-06 14:06 ` Gleb Natapov
2009-10-07 18:50 ` Olivier Galibert
2009-10-07 18:59 ` Gleb Natapov
2009-10-07 20:10 ` Olivier Galibert
2009-10-07 20:47 ` Gleb Natapov
2009-10-06 10:49 ` Arnd Bergmann
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=1254837003.21044.283.camel@laptop \
--to=peterz@infradead.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox