From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@kernel.org>, Eric B Munson <emunson@akamai.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v7 3/6] mm: Introduce VM_LOCKONFAULT
Date: Wed, 26 Aug 2015 17:35:41 +0200 [thread overview]
Message-ID: <55DDDCCD.5000908@suse.cz> (raw)
In-Reply-To: <20150826072016.GD25196@dhcp22.suse.cz>
On 08/26/2015 09:20 AM, Michal Hocko wrote:
> On Tue 25-08-15 15:03:00, Eric B Munson wrote:
> [...]
>> Would you drop your objections to the VMA flag if I drop the portions of
>> the patch that expose it to userspace?
>>
>> The rework to not use the VMA flag is pretty sizeable and is much more
>> ugly IMO. I know that you are not wild about using bit 30 of 32 for
>> this, but perhaps we can settle on not exporting it to userspace so we
>> can reclaim it if we really need it in the future?
>
> Yes, that would be definitely more acceptable for me. I do understand
> that you are not wild about changing mremap behavior.
+1
--
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:[~2015-08-26 15:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 5:22 [PATCH v7 0/6] Allow user to request memory to be locked on page fault Eric B Munson
2015-08-09 5:22 ` [PATCH v7 1/6] mm: mlock: Refactor mlock, munlock, and munlockall code Eric B Munson
2015-08-12 9:42 ` Michal Hocko
2015-08-09 5:22 ` [PATCH v7 2/6] mm: mlock: Add new mlock system call Eric B Munson
2015-08-12 9:45 ` Michal Hocko
2015-08-09 5:22 ` [PATCH v7 3/6] mm: Introduce VM_LOCKONFAULT Eric B Munson
2015-08-12 11:59 ` Michal Hocko
2015-08-19 21:33 ` Eric B Munson
2015-08-20 7:53 ` Vlastimil Babka
2015-08-20 7:56 ` Michal Hocko
2015-08-20 17:03 ` Eric B Munson
2015-08-21 7:25 ` Michal Hocko
2015-08-21 18:31 ` Eric B Munson
2015-08-24 10:17 ` Konstantin Khlebnikov
2015-08-24 13:30 ` Vlastimil Babka
2015-08-24 13:50 ` Konstantin Khlebnikov
2015-08-24 14:27 ` Vlastimil Babka
2015-08-24 15:09 ` Eric B Munson
2015-08-24 15:46 ` Konstantin Khlebnikov
2015-08-24 15:55 ` Eric B Munson
2015-08-24 16:22 ` Konstantin Khlebnikov
2015-08-24 17:00 ` Eric B Munson
2015-08-24 18:53 ` Konstantin Khlebnikov
2015-08-24 20:26 ` Eric B Munson
2015-08-25 13:41 ` Michal Hocko
2015-08-25 13:55 ` Vlastimil Babka
2015-08-25 14:29 ` Michal Hocko
2015-08-25 13:58 ` Konstantin Khlebnikov
2015-08-25 14:29 ` Eric B Munson
2015-08-25 18:58 ` Michal Hocko
2015-08-25 19:03 ` Eric B Munson
2015-08-26 7:20 ` Michal Hocko
2015-08-26 15:35 ` Vlastimil Babka [this message]
2015-08-09 5:22 ` [PATCH v7 4/6] mm: mlock: Add mlock flags to enable VM_LOCKONFAULT usage Eric B Munson
2015-08-09 5:22 ` [PATCH v7 5/6] selftests: vm: Add tests for lock on fault Eric B Munson
2015-08-09 5:22 ` [PATCH v7 6/6] mips: Add entry for new mlock2 syscall Eric B Munson
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=55DDDCCD.5000908@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=emunson@akamai.com \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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).