From: Rik van Riel <riel@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v2
Date: Wed, 13 Jun 2012 16:38:15 -0400 [thread overview]
Message-ID: <4FD8FA37.10103@redhat.com> (raw)
In-Reply-To: <20120613203103.GG11413@one.firstfloor.org>
On 06/13/2012 04:31 PM, Andi Kleen wrote:
> On Wed, Jun 13, 2012 at 04:24:47PM -0400, Rik van Riel wrote:
>> This would also be useful for emulators such as qemu-kvm,
>> which want the guest memory to be 2MB aligned.
>
> hugetlbfs does implicit align, so right now I mash
> the two together and use up many of the remaining bits
>
> If you want align different than page sizes you may need
> to go 64bits with the flags.
All alignment is a power of two, so six bits should
be enough for up to 2^64 pages :)
> Is there a use case for alignment independent of page sizes?
No, but page size differs per architecture and it
would be nice if we could share arch_get_unmapped_area
and related code in mm/, instead of every architecture
having its own.
In fact, that is what I am working on right now, and
my current road block is the page colouring code :)
--
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:[~2012-06-13 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 23:13 [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v2 Andi Kleen
2012-06-13 20:24 ` Rik van Riel
2012-06-13 20:31 ` Andi Kleen
2012-06-13 20:38 ` Rik van Riel [this message]
2012-06-15 10:35 ` Michal Hocko
2012-06-16 7:28 ` Kamezawa Hiroyuki
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=4FD8FA37.10103@redhat.com \
--to=riel@redhat.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).