From: Andi Kleen <ak@linux.intel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: mtk.manpages@gmail.com, Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Hillf Danton <dhillf@gmail.com>
Subject: Re: [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v6
Date: Mon, 22 Oct 2012 19:28:44 -0700 [thread overview]
Message-ID: <20121023022844.GQ2095@tassilo.jf.intel.com> (raw)
In-Reply-To: <1350956664.2728.19.camel@pasglop>
On Tue, Oct 23, 2012 at 12:44:24PM +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2012-10-22 at 17:53 +0200, Michael Kerrisk (man-pages) wrote:
>
> > This is all seems to make an awful muck of the API...
>
> .../...
>
> > There seems to be a reasonable argument here for an mmap3() with a
> > 64-bit flags argument...
>
> I tend to agree. There's a similar issue happening when we try to shovel
Could you comment on the expect range of page sizes on PPC?
I looked at this again and I don't think we have anywhere near true 28 flags
so far. The man page currently only lists 16 (including MAP_UNUS^INITIALIZED)
So I don't see why I can't have 6 bits from that.
I have no idea why the MAP_UNINITIALIZED flag was put into this strange
location anyways instead of directly after the existing flags or just
into one of the unused slots.
I suppose I could put my bits before it, there's plenty of space.
Existing flags on x86:
#define MAP_SHARED 0x01 /* Share changes */
#define MAP_PRIVATE 0x02 /* Changes are private */
4 unused
8 unused
#define MAP_FIXED 0x10 /* Interpret addr exactly */
#define MAP_ANONYMOUS 0x20 /* don't use a file */
0x40 unused
#define MAP_GROWSDOWN 0x0100 /* stack-like segment */
0x200 unused
0x400 unused
#define MAP_DENYWRITE 0x0800 /* ETXTBSY */
#define MAP_EXECUTABLE 0x1000 /* mark it as an executable */
#define MAP_LOCKED 0x2000 /* pages are locked */
#define MAP_NORESERVE 0x4000 /* don't check for reservations */
#define MAP_POPULATE 0x8000 /* populate (prefault) pagetables */
#define MAP_NONBLOCK 0x10000 /* do not block on IO */
#define MAP_STACK 0x20000 /* give out an address that is best suited for process/thread stacks */
#define MAP_HUGETLB 0x40000 /* create a huge page mapping */
/* all free here: 6 bits for me? 0x80000..0x1000000 */
# define MAP_UNINITIALIZED 0x4000000 /* For anonymous mmap, memory could be uninitialized */
/* more free bits. */
Overall it seems there's no real shortage of bits.
> things into protection bits, like we do with SAO (strong access
> ordering) and want to do with per-page endian on embedded.
mprotect already does this.
Unless someone finds a good reason why this can't work I'll just move
the range to 0x80000..0x1000000.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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-10-23 2:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 16:48 Andi Kleen
2012-10-20 3:39 ` Hillf Danton
2012-10-22 11:27 ` Michael Kerrisk
2012-10-22 13:27 ` Andi Kleen
2012-10-22 13:35 ` Andi Kleen
2012-10-22 13:56 ` Michael Kerrisk (man-pages)
2012-10-22 15:36 ` Andi Kleen
2012-10-22 15:53 ` Michael Kerrisk (man-pages)
2012-10-22 16:11 ` Andi Kleen
2012-10-22 16:23 ` Michael Kerrisk (man-pages)
2012-10-22 16:29 ` Andi Kleen
2012-10-22 16:42 ` Michael Kerrisk (man-pages)
2012-10-23 1:45 ` Benjamin Herrenschmidt
2012-10-23 1:44 ` Benjamin Herrenschmidt
2012-10-23 2:28 ` Andi Kleen [this message]
2012-10-23 7:37 ` Michael Kerrisk (man-pages)
2012-10-23 13:39 ` Andi Kleen
2012-10-23 22:56 ` Valdis.Kletnieks
2012-10-22 21:39 ` Andrew Morton
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=20121023022844.GQ2095@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=benh@kernel.crashing.org \
--cc=dhillf@gmail.com \
--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