From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: mtk.manpages@gmail.com
Cc: Andi Kleen <ak@linux.intel.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: Tue, 23 Oct 2012 12:44:24 +1100 [thread overview]
Message-ID: <1350956664.2728.19.camel@pasglop> (raw)
In-Reply-To: <CAKgNAki=AL+KdYDdYnE8ZhjK-tUf5cZ163BWPe6GRM0rpi-z7w@mail.gmail.com>
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
things into protection bits, like we do with SAO (strong access
ordering) and want to do with per-page endian on embedded.
It think we need a pile of additional flag space.
Cheers,
Ben.
--
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 1:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 16:48 [PATCH] MM: Support more pagesizes for MAP_HUGETLB/SHM_HUGETLB v6 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 [this message]
2012-10-23 2:28 ` Andi Kleen
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=1350956664.2728.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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;
as well as URLs for NNTP newsgroup(s).