From: Eric B Munson <emunson@mgebm.net>
To: Michal Hocko <mhocko@kernel.org>, Eric B Munson <emunson@akamai.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Jonathan Corbet <corbet@lwn.net>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v8 3/6] mm: Introduce VM_LOCKONFAULT
Date: Tue, 01 Sep 2015 08:51:35 -0400 [thread overview]
Message-ID: <450C6E20-C941-4BE2-853B-0203C6BE38F6@mgebm.net> (raw)
In-Reply-To: <20150828141829.GD5301@dhcp22.suse.cz>
On August 28, 2015 10:18:30 AM EDT, Michal Hocko <mhocko@kernel.org> wrote:
>
>Why do we need to export this? Neither of the consumers care and should
>care. VM_LOCKONFAULT should never be set without VM_LOCKED which is the
>only thing that we should care about.
I am out of the office and I don't know if I will be back in time to respin this series without this hunk. Andrew, can you remove the export of VM_LOCKONFAULT to the rmap code?
Thank,
Eric
--
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-09-01 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 18:24 [PATCH v8 0/6] Allow user to request memory to be locked on page fault Eric B Munson
2015-08-26 18:24 ` [PATCH v8 1/6] mm: mlock: Refactor mlock, munlock, and munlockall code Eric B Munson
2015-08-26 18:24 ` [PATCH v8 2/6] mm: mlock: Add new mlock system call Eric B Munson
2015-08-26 18:24 ` [PATCH v8 3/6] mm: Introduce VM_LOCKONFAULT Eric B Munson
2015-08-28 14:18 ` Michal Hocko
2015-08-28 19:34 ` Eric B Munson
2015-08-31 8:53 ` Michal Hocko
2015-09-01 12:51 ` Eric B Munson [this message]
2015-08-28 14:54 ` Vlastimil Babka
2015-08-26 18:24 ` [PATCH v8 4/6] mm: mlock: Add mlock flags to enable VM_LOCKONFAULT usage Eric B Munson
2015-08-28 14:31 ` Michal Hocko
2015-08-28 14:32 ` Michal Hocko
2015-08-26 18:24 ` [PATCH v8 5/6] selftests: vm: Add tests for lock on fault Eric B Munson
2015-08-26 18:24 ` [PATCH v8 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=450C6E20-C941-4BE2-853B-0203C6BE38F6@mgebm.net \
--to=emunson@mgebm.net \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--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 \
--cc=vbabka@suse.cz \
/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