From: Florian Weimer <fweimer@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [patch] mremap.2: Add description of old_size == 0 functionality
Date: Mon, 25 Sep 2017 14:40:42 +0200 [thread overview]
Message-ID: <e301609c-b2ac-24d1-c349-8d25e5123258@redhat.com> (raw)
In-Reply-To: <20170925123508.pzjbe7wgwagnr5li@dhcp22.suse.cz>
On 09/25/2017 02:35 PM, Michal Hocko wrote:
> What would be the usecase. I mean why don't you simply create a new
> mapping by a plain mmap when you have no guarantee about the same
> content?
I plan to use it for creating an unbounded number of callback thunks at
run time, from a single set of pages in libc.so, in case we need this
functionality.
The idea is to duplicate existing position-independent machine code in
libc.so, prefixed by a data mapping which controls its behavior. Each
data/code combination would only give us a fixed number of thunks, so
we'd need to create a new mapping to increase the total number.
Instead, we could re-map the code from the executable in disk, but not
if chroot has been called or glibc has been updated on disk. Creating
an alias mapping does not have these problems.
Another application (but that's for anonymous memory) would be to
duplicate class metadata in a Java-style VM, so that you can use bits in
the class pointer in each Java object (which is similar to the vtable
pointer in C++) for the garbage collector, without having to mask it
when accessing the class metadata in regular (mutator) code.
Thanks,
Florian
--
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:[~2017-09-25 12:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170915213745.6821-1-mike.kravetz@oracle.com>
2017-09-15 21:53 ` Mike Kravetz
2017-09-18 13:45 ` Florian Weimer
2017-09-18 17:11 ` Mike Kravetz
2017-09-19 12:11 ` Florian Weimer
2017-09-19 21:42 ` [patch v2] " Mike Kravetz
2017-09-20 7:25 ` Michael Kerrisk (man-pages)
2017-09-25 12:36 ` Michal Hocko
2017-09-25 12:40 ` Michael Kerrisk (man-pages)
2017-09-25 16:33 ` Mike Kravetz
2017-09-25 19:26 ` Michael Kerrisk (man-pages)
2017-09-25 12:35 ` [patch] " Michal Hocko
2017-09-25 12:40 ` Florian Weimer [this message]
2017-09-25 12:52 ` Michal Hocko
2017-09-25 13:16 ` Florian Weimer
2017-09-25 14:52 ` Michal Hocko
2017-09-25 14:54 ` Florian Weimer
2017-09-18 1:52 ` Jann Horn
2017-09-18 17:19 ` Mike Kravetz
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=e301609c-b2ac-24d1-c349-8d25e5123258@redhat.com \
--to=fweimer@redhat.com \
--cc=aarcange@redhat.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--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