From: Adam Litke <agl@us.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: libhugetlbfs-devel@lists.sourceforge.net
Subject: [RFD] Hugetlb: Allowing hugetlb regions to be closed
Date: Thu, 18 May 2006 10:23:58 -0500 [thread overview]
Message-ID: <1147965839.24029.229.camel@localhost.localdomain> (raw)
Please correct me if I am wrong in any of the following...
On powerpc, once a region of the address space has been 'opened' for use
with hugetlb pages this region can never again contain normal pages for
the remaining life of the process -- even if all hugetlb mappings have
been unmapped from this region.
The above approach is nice and simple, but a bit restrictive too. Would
people be opposed to a patch which provides methods for closing low/high
hugetlb areas and logic in arch_get_unmapped_area() to perform the
closing? My thought would be to try closing only in the full_search:
case (so the fast path is left untouched.
As for why I want this... I have an application (libhugetlbfs), which
provides hugetlb pages to applications in an abstracted manner. There
are situations where the library creates a hugetlb area and needs to
later replace it with normal pages. The main case this will happen is
for a hugetlb-backed malloc area.
Thoughts?
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
reply other threads:[~2006-05-18 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1147965839.24029.229.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=libhugetlbfs-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
/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