linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric B Munson <emunson@akamai.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: mtk.manpages@gmail.com, Michal Hocko <mhocko@suse.cz>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-man@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall
Date: Fri, 11 Sep 2015 10:57:12 -0400	[thread overview]
Message-ID: <20150911145712.GA3452@akamai.com> (raw)
In-Reply-To: <55F14E05.6020304@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On Thu, 10 Sep 2015, Vlastimil Babka wrote:

> On 08/31/2015 04:20 PM, 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>
> > Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Looks like I acked v1 too late and not v2, so:
> 
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> 
> However, looks like it won't be in Linux 4.3 so that part is outdated.
> Also, what about glibc wrapper for mlock2()? Does it have to come before or
> after the manpage and who gets it in?

V3 now has an updated version, hopefully mlock2 hits the 4.4 merge
window.

I don't know about the glibc wrapper, are we expected to write one
ourselves?  Will they even take it?  They haven't been the most open
minded about taking wrappers for system calls that are unique to Linux
in the past.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-09-11 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 14:20 [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall Eric B Munson
2015-09-10  9:31 ` Vlastimil Babka
2015-09-11 14:57   ` Eric B Munson [this message]
2015-09-11 15:16     ` 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=20150911145712.GA3452@akamai.com \
    --to=emunson@akamai.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).