[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150911145712.GA3452@akamai.com>
Date: Fri, 11 Sep 2015 10:57:12 -0400
From: Eric B Munson <emunson@...mai.com>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: mtk.manpages@...il.com, Michal Hocko <mhocko@...e.cz>,
Jonathan Corbet <corbet@....net>, linux-man@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall
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@...mai.com>
> > Acked-by: Michal Hocko <mhocko@...e.com>
>
> Looks like I acked v1 too late and not v2, so:
>
> Acked-by: Vlastimil Babka <vbabka@...e.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.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists