From: Andrew Morton <akpm@linux-foundation.org>
To: Eric B Munson <emunson@akamai.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Michal Hocko <mhocko@suse.cz>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault
Date: Wed, 8 Jul 2015 10:00:08 -0700 [thread overview]
Message-ID: <20150708100008.e8a000ec.akpm@linux-foundation.org> (raw)
In-Reply-To: <20150708132302.GB4669@akamai.com>
On Wed, 8 Jul 2015 09:23:02 -0400 Eric B Munson <emunson@akamai.com> wrote:
> > I don't know whether these syscalls should be documented via new
> > manpages, or if we should instead add them to the existing
> > mlock/munlock/mlockall manpages. Michael, could you please advise?
> >
>
> Thanks for adding the series. I owe you several updates (getting the
> new syscall right for all architectures and a set of tests for the new
> syscalls). Would you prefer a new pair of patches or I update this set?
It doesn't matter much. I guess a full update will be more convenient
at your end.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Eric B Munson <emunson@akamai.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Michal Hocko <mhocko@suse.cz>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault
Date: Wed, 08 Jul 2015 17:00:08 +0000 [thread overview]
Message-ID: <20150708100008.e8a000ec.akpm@linux-foundation.org> (raw)
In-Reply-To: <20150708132302.GB4669@akamai.com>
On Wed, 8 Jul 2015 09:23:02 -0400 Eric B Munson <emunson@akamai.com> wrote:
> > I don't know whether these syscalls should be documented via new
> > manpages, or if we should instead add them to the existing
> > mlock/munlock/mlockall manpages. Michael, could you please advise?
> >
>
> Thanks for adding the series. I owe you several updates (getting the
> new syscall right for all architectures and a set of tests for the new
> syscalls). Would you prefer a new pair of patches or I update this set?
It doesn't matter much. I guess a full update will be more convenient
at your end.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Eric B Munson <emunson@akamai.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Michal Hocko <mhocko@suse.cz>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault
Date: Wed, 8 Jul 2015 10:00:08 -0700 [thread overview]
Message-ID: <20150708100008.e8a000ec.akpm@linux-foundation.org> (raw)
In-Reply-To: <20150708132302.GB4669@akamai.com>
On Wed, 8 Jul 2015 09:23:02 -0400 Eric B Munson <emunson@akamai.com> wrote:
> > I don't know whether these syscalls should be documented via new
> > manpages, or if we should instead add them to the existing
> > mlock/munlock/mlockall manpages. Michael, could you please advise?
> >
>
> Thanks for adding the series. I owe you several updates (getting the
> new syscall right for all architectures and a set of tests for the new
> syscalls). Would you prefer a new pair of patches or I update this set?
It doesn't matter much. I guess a full update will be more convenient
at your end.
--
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-07-08 17:00 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 17:03 [PATCH V3 0/5] Allow user to request memory to be locked on page fault Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` [PATCH V3 1/5] mm: mlock: Refactor mlock, munlock, and munlockall code Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` [PATCH V3 2/5] mm: mlock: Add new mlock, munlock, and munlockall system calls Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-08 6:46 ` Heiko Carstens
2015-07-08 6:46 ` Heiko Carstens
2015-07-08 6:46 ` Heiko Carstens
2015-07-08 6:46 ` Heiko Carstens
2015-07-08 6:46 ` Heiko Carstens
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
2015-07-08 7:02 ` Geert Uytterhoeven
[not found] ` <1436288623-13007-3-git-send-email-emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-08 11:06 ` Catalin Marinas
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-08 19:23 ` Jonathan Corbet
2015-07-08 19:23 ` Jonathan Corbet
2015-07-08 19:23 ` Jonathan Corbet
2015-07-08 20:34 ` Eric B Munson
2015-07-08 20:34 ` Eric B Munson
2015-07-08 21:17 ` Jonathan Corbet
2015-07-08 21:17 ` Jonathan Corbet
2015-07-08 21:17 ` Jonathan Corbet
2015-07-08 21:17 ` Jonathan Corbet
2015-07-08 21:17 ` Jonathan Corbet
2015-07-08 21:17 ` Jonathan Corbet
2015-07-09 18:46 ` Eric B Munson
2015-07-09 18:46 ` Eric B Munson
2015-07-10 16:11 ` Jonathan Corbet
2015-07-10 16:11 ` Jonathan Corbet
2015-07-10 16:11 ` Jonathan Corbet
[not found] ` <20150710101118.5d04d627-T1hC0tSOHrs@public.gmane.org>
2015-07-10 16:19 ` Eric B Munson
2015-07-10 16:19 ` Eric B Munson
2015-07-10 16:19 ` Eric B Munson
2015-07-21 15:35 ` Vlastimil Babka
2015-07-21 15:35 ` Vlastimil Babka
2015-07-21 15:35 ` Vlastimil Babka
2015-07-07 17:03 ` [PATCH V3 4/5] mm: mmap: Add mmap flag to request VM_LOCKONFAULT Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-18 19:11 ` Paul Gortmaker
2015-07-18 19:11 ` Paul Gortmaker
2015-07-20 20:40 ` Chris Metcalf
2015-07-20 20:40 ` Chris Metcalf
2015-07-20 20:40 ` Chris Metcalf
2015-07-21 15:37 ` Eric B Munson
2015-07-22 14:10 ` Paul Gortmaker
2015-07-22 14:10 ` Paul Gortmaker
2015-07-22 14:10 ` Paul Gortmaker
[not found] ` <1436288623-13007-1-git-send-email-emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-07-07 17:03 ` [PATCH V3 5/5] selftests: vm: Add tests for lock on fault Eric B Munson
2015-07-07 17:03 ` Eric B Munson
2015-07-07 17:03 ` Eric B Munson
[not found] ` <1436288623-13007-6-git-send-email-emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-07-07 21:51 ` Andrew Morton
2015-07-07 21:51 ` Andrew Morton
2015-07-07 21:51 ` Andrew Morton
2015-07-07 21:16 ` [PATCH V3 0/5] Allow user to request memory to be locked on page fault Andrew Morton
2015-07-07 21:16 ` Andrew Morton
2015-07-07 21:16 ` Andrew Morton
2015-07-07 21:16 ` Andrew Morton
2015-07-08 13:23 ` Eric B Munson
2015-07-08 13:23 ` Eric B Munson
2015-07-08 17:00 ` Andrew Morton [this message]
2015-07-08 17:00 ` Andrew Morton
2015-07-08 17:00 ` Andrew Morton
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=20150708100008.e8a000ec.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=emunson@akamai.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.cz \
--cc=mtk.manpages@gmail.com \
--cc=shuahkh@osg.samsung.com \
--cc=sparclinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.