From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <miso@dhcp22.suse.cz>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH 1/2] mmap.2: clarify MAP_LOCKED semantic
Date: Wed, 11 May 2016 13:18:05 +0200 [thread overview]
Message-ID: <573314ED.4090704@infradead.org> (raw)
In-Reply-To: <57331275.9000805@infradead.org>
On 05/11/2016 01:07 PM, Peter Zijlstra wrote:
> On 05/13/2015 04:38 PM, Michal Hocko wrote:
>>
>> This patch makes the semantic of MAP_LOCKED explicit and suggest using
>> mmap + mlock as the only way to guarantee no later major page faults.
>>
>
> URGH, this really blows chunks. It basically means MAP_LOCKED is
> pointless cruft and we might as well remove it.
>
> Why not fix it proper?
OK; after having been pointed at this discussion, it seems I reacted rather
too hasty in that I didn't read all the previous threads.
From that it appears fixing this proper is indeed rather hard, and we
should
indeed consider MAP_LOCKED broken. At which point I would've worded the
manpage update stronger, but alas.
Sorry for the noise.
--
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: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <miso@dhcp22.suse.cz>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH 1/2] mmap.2: clarify MAP_LOCKED semantic
Date: Wed, 11 May 2016 13:18:05 +0200 [thread overview]
Message-ID: <573314ED.4090704@infradead.org> (raw)
In-Reply-To: <57331275.9000805@infradead.org>
On 05/11/2016 01:07 PM, Peter Zijlstra wrote:
> On 05/13/2015 04:38 PM, Michal Hocko wrote:
>>
>> This patch makes the semantic of MAP_LOCKED explicit and suggest using
>> mmap + mlock as the only way to guarantee no later major page faults.
>>
>
> URGH, this really blows chunks. It basically means MAP_LOCKED is
> pointless cruft and we might as well remove it.
>
> Why not fix it proper?
OK; after having been pointed at this discussion, it seems I reacted rather
too hasty in that I didn't read all the previous threads.
From that it appears fixing this proper is indeed rather hard, and we
should
indeed consider MAP_LOCKED broken. At which point I would've worded the
manpage update stronger, but alas.
Sorry for the noise.
next prev parent reply other threads:[~2016-05-11 11:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:38 [PATCH 0/2] man-pages: clarify MAP_LOCKED semantic Michal Hocko
2015-05-13 14:38 ` Michal Hocko
[not found] ` <1431527892-2996-1-git-send-email-miso-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-05-13 14:38 ` [PATCH 1/2] mmap.2: " Michal Hocko
2015-05-13 14:38 ` Michal Hocko
2015-05-13 14:38 ` Michal Hocko
2015-05-13 14:45 ` Eric B Munson
[not found] ` <20150513144506.GD1227-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-05-13 14:48 ` Eric B Munson
2015-05-13 14:48 ` Eric B Munson
2015-05-14 8:01 ` Michal Hocko
2015-05-14 8:01 ` Michal Hocko
2015-05-14 8:01 ` Michal Hocko
2015-05-14 13:36 ` Michael Kerrisk (man-pages)
2015-05-14 13:36 ` Michael Kerrisk (man-pages)
[not found] ` <1431527892-2996-2-git-send-email-miso-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2016-05-11 11:07 ` Peter Zijlstra
2016-05-11 11:07 ` Peter Zijlstra
2016-05-11 11:07 ` Peter Zijlstra
2016-05-11 11:18 ` Peter Zijlstra [this message]
2016-05-11 11:18 ` Peter Zijlstra
[not found] ` <57331275.9000805-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-05-11 11:32 ` Michal Hocko
2016-05-11 11:32 ` Michal Hocko
2016-05-11 11:32 ` Michal Hocko
2015-05-13 14:38 ` [PATCH 2/2] mmap2: clarify MAP_POPULATE Michal Hocko
2015-05-13 14:38 ` Michal Hocko
[not found] ` <1431527892-2996-3-git-send-email-miso-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-05-13 14:47 ` Eric B Munson
2015-05-13 14:47 ` Eric B Munson
2015-05-14 13:36 ` Michael Kerrisk (man-pages)
2015-05-14 13:36 ` Michael Kerrisk (man-pages)
2015-05-15 0:13 ` David Rientjes
2015-05-15 0:13 ` David Rientjes
2015-05-18 9:12 ` [PATCH 0/2] man-pages: clarify MAP_LOCKED semantic Michal Hocko
2015-05-18 9:12 ` Michal Hocko
2015-05-18 9:12 ` Michal Hocko
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=573314ED.4090704@infradead.org \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=miso@dhcp22.suse.cz \
--cc=mtk.manpages@gmail.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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.