From: Hugh Dickins <hugh@veritas.com>
To: Adam Litke <agl@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-mm@kvack.org,
David Gibson <david@gibson.dropbear.id.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hugetlb: powerpc: Actively close unused htlb regions on vma close
Date: Fri, 2 Jun 2006 17:43:13 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606021737310.26864@blonde.wat.veritas.com> (raw)
In-Reply-To: <1149257287.9693.6.camel@localhost.localdomain>
On Fri, 2 Jun 2006, Adam Litke wrote:
>
> On powerpc, each segment can contain pages of only one size. When a
> hugetlb mapping is requested, a segment is located and marked for use
> with huge pages. This is a uni-directional operation -- hugetlb
> segments are never marked for use again with normal pages. For long
> running processes which make use of a combination of normal and hugetlb
> mappings, this behavior can unduly constrain the virtual address space.
>
> The following patch introduces a architecture-specific vm_ops.close()
> hook. For all architectures besides powerpc, this is a no-op. On
> powerpc, the low and high segments are scanned to locate empty hugetlb
> segments which can be made available for normal mappings. Comments?
Wouldn't hugetlb_free_pgd_range be a better place to do that kind of
thing, all within arch/powerpc, no need for arch_hugetlb_close_vma etc?
Hugh
--
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:[~2006-06-02 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 14:08 Adam Litke
2006-06-02 15:17 ` Dave Hansen
2006-06-02 16:47 ` Adam Litke
2006-06-02 16:43 ` Hugh Dickins [this message]
2006-06-02 16:49 ` Adam Litke
2006-06-02 20:06 ` Christoph Lameter
2006-06-02 20:57 ` Adam Litke
2006-06-02 21:08 ` Christoph Lameter
2006-06-09 8:49 ` David Gibson
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=Pine.LNX.4.64.0606021737310.26864@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=agl@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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