From: Andi Kleen <ak@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v3
Date: Thu, 11 Oct 2012 16:35:41 -0700 [thread overview]
Message-ID: <20121011233541.GN2095@tassilo.jf.intel.com> (raw)
In-Reply-To: <20121009151907.3f61ebca.akpm@linux-foundation.org>
> Alas, include/asm-generic/mman.h doesn't exist now.
git resolved it automagically
>
> Does this change touch all the hugetlb-capable architectures?
I took a look at this again. So not every hugetlb capable architecture
needs it, only architectures with multiple hugetlb page sizes.
This is only x86, tile, powerpc
I looked at tile and powerpc and they both have configurable
hugetlb page sizes. So it's somewhat awkward to add defines
for them.
One disadvantage of this is also the user programs would need
to know the page sizes that are configured. That is definitely
awkward, but I don't know of any way around that.
Luckily there's a way in /sys to query this.
-Andi
>
> z:/usr/src/linux-3.6> grep -rl MAP_HUGETLB arch
> arch/alpha/include/asm/mman.h
> arch/xtensa/include/asm/mman.h
> arch/parisc/include/asm/mman.h
> arch/tile/include/asm/mman.h
> arch/sparc/include/asm/mman.h
> arch/powerpc/include/asm/mman.h
> arch/mips/include/asm/mman.h
--
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>
prev parent reply other threads:[~2012-10-11 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 22:24 Resubmitting 1GB page shm patchkit Andi Kleen
2012-10-03 22:24 ` [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v3 Andi Kleen
2012-10-09 22:19 ` Andrew Morton
2012-10-10 2:25 ` Andi Kleen
2012-10-11 23:35 ` Andi Kleen [this message]
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=20121011233541.GN2095@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.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