From: Michal Hocko <mhocko@kernel.org>
To: Eric B Munson <emunson@akamai.com>
Cc: mtk.manpages@gmail.com, Vlastimil Babka <vbabka@suse.cz>,
Jonathan Corbet <corbet@lwn.net>,
linux-man@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mlock.2: mlock2.2: Add entry to for new mlock2 syscall
Date: Mon, 31 Aug 2015 11:23:01 +0200 [thread overview]
Message-ID: <20150831092300.GE29723@dhcp22.suse.cz> (raw)
In-Reply-To: <1440787391-30298-1-git-send-email-emunson@akamai.com>
On Fri 28-08-15 14:43:11, Eric B Munson wrote:
> Update the mlock.2 man page with information on mlock2() and the new
> mlockall() flag MCL_ONFAULT.
>
> Signed-off-by: Eric B Munson <emunson@akamai.com>
> Cc: Michal Hocko <mhocko@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
I am not familiar with the format much so I am just looking at the text
and that looks reasonable to me. Just one note below:
> Cc: Vlastimil Babka <vbabka@suse.cz>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-man@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> ---
> man2/mlock.2 | 109 +++++++++++++++++++++++++++++++++++++++++++++++++++-------
> man2/mlock2.2 | 1 +
> 2 files changed, 97 insertions(+), 13 deletions(-)
> create mode 100644 man2/mlock2.2
>
> diff --git a/man2/mlock.2 b/man2/mlock.2
> index 79c544d..8f51926 100644
> --- a/man2/mlock.2
> +++ b/man2/mlock.2
[...]
> +The
> +.I flags
> +argument can be either 0 or the following constant:
> +.TP 1.2i
> +.B MLOCK_ONFAULT
> +Lock pages that are currently resident and mark the entire range to have
> +pages locked when they are faulted in.
@faulted in@populated by the page fault@.
would be probably better.
[...]
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2015-08-31 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 18:43 Eric B Munson
2015-08-28 18:47 ` Eric B Munson
2015-08-31 9:23 ` Michal Hocko [this message]
2015-09-09 12:00 ` Vlastimil Babka
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=20150831092300.GE29723@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=corbet@lwn.net \
--cc=emunson@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--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
all inboxes | Powered by JetHome®