From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Piotr Kwapulinski <kwapulinski.piotr@gmail.com>
Cc: akpm@linux-foundation.org, mhocko@suse.com,
mtk.manpages@gmail.com, cmetcalf@mellanox.com, arnd@arndb.de,
viro@zeniv.linux.org.uk, mszeredi@suse.cz, dave@stgolabs.net,
vbabka@suse.cz, mingo@kernel.org, dan.j.williams@intel.com,
dave.hansen@linux.intel.com, koct9i@gmail.com,
hannes@cmpxchg.org, jack@suse.cz, xiexiuqi@huawei.com,
iamjoonsoo.kim@lge.com, oleg@redhat.com,
gang.chen.5i5j@gmail.com, aarcange@redhat.com,
aryabinin@virtuozzo.com, rientjes@google.com, denc716@gmail.com,
toshi.kani@hpe.com, ldufour@linux.vnet.ibm.com,
kuleshovmail@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 0/3] mm/mmap.c: don't unmap the overlapping VMA(s)
Date: Sun, 3 Apr 2016 00:54:30 +0300 [thread overview]
Message-ID: <20160402215430.GA100607@black.fi.intel.com> (raw)
In-Reply-To: <1459624654-7955-1-git-send-email-kwapulinski.piotr@gmail.com>
On Sat, Apr 02, 2016 at 09:17:31PM +0200, Piotr Kwapulinski wrote:
> @@ -19,6 +19,7 @@
> #define MAP_TYPE 0x0f /* Mask for type of mapping */
> #define MAP_FIXED 0x10 /* Interpret addr exactly */
> #define MAP_ANONYMOUS 0x20 /* don't use a file */
> +#define MAP_DONTUNMAP 0x40 /* don't unmap overlapping VMA */
NAK.
arch/powerpc/include/uapi/asm/mman.h:#define MAP_NORESERVE 0x40 /* don't reserve swap pages */
arch/sparc/include/uapi/asm/mman.h:#define MAP_NORESERVE 0x40 /* don't reserve swap pages */
arch/x86/include/uapi/asm/mman.h:#define MAP_32BIT 0x40 /* only give out 32bit addresses */
--
Kirill A. Shutemov
--
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:[~2016-04-02 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 19:17 [PATCH 0/3] mm/mmap.c: don't unmap the overlapping VMA(s) Piotr Kwapulinski
2016-04-02 19:17 ` [PATCH 1/3] man/mmap.2: " Piotr Kwapulinski
2016-04-02 19:17 ` [PATCH 2/3] mm/mremap.c: " Piotr Kwapulinski
2016-04-02 19:17 ` [PATCH 3/3] man/mremap.2: " Piotr Kwapulinski
2016-04-02 21:54 ` Kirill A. Shutemov [this message]
2016-04-03 5:52 ` [PATCH 0/3] mm/mmap.c: " Konstantin Khlebnikov
2016-04-04 7:31 ` Michal Hocko
2016-04-04 15:26 ` Vlastimil Babka
2016-04-07 16:11 ` Piotr Kwapulinski
2016-04-07 16:31 ` Michal Hocko
2016-04-08 15:32 ` Piotr Kwapulinski
2016-04-07 16:20 ` Piotr Kwapulinski
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=20160402215430.GA100607@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=cmetcalf@mellanox.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=denc716@gmail.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=koct9i@gmail.com \
--cc=kuleshovmail@gmail.com \
--cc=kwapulinski.piotr@gmail.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=mszeredi@suse.cz \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=toshi.kani@hpe.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=xiexiuqi@huawei.com \
/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).