linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: 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 18:42:22 +0200	[thread overview]
Message-ID: <CAKgNAkhn+kTAq6_VKB3GjwwZGD-YOKE67=4fp+SR=1Lbhz7Bxg@mail.gmail.com> (raw)
In-Reply-To: <20121022162929.GN2095@tassilo.jf.intel.com>

On Mon, Oct 22, 2012 at 6:29 PM, Andi Kleen <ak@linux.intel.com> wrote:
>> Since PowerPC already allows 16GB page sizes, doesn't there need to be
>> allowance for the possibility of future expansion? Choosing a larger
>> minimum size (like 2^16) would allow that. Does the minimum size need
>> to be 16k? (Surely, if you want a HUGEPAGE, you want a bigger page
>> than that? I am not sure.)
>
> Some architectures have configurable huge page sizes, so it depends on
> the user. I thought 16K is reasonable.  Can make it larger too.
>
> But I personally consider even 16GB pages somewhat too big.

I do not know the answer course ;-). Just thought that it was worth
emphasizing that some system already allows the upper limit you
propose. It seems inevitable that some other system will allow
something even bigger.

Anyway, I got distracted from my earlier more important point. This
proposed change will chew up most (all?) of the remaining bit-space in
'flags'. This seems like a mistake from a future extensibility point
of view... It sounds a lot like you'll force someone else to write and
deploy mmap3()...

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/

--
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>

  reply	other threads:[~2012-10-22 16:42 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) [this message]
2012-10-23  1:45                 ` Benjamin Herrenschmidt
2012-10-23  1:44             ` Benjamin Herrenschmidt
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='CAKgNAkhn+kTAq6_VKB3GjwwZGD-YOKE67=4fp+SR=1Lbhz7Bxg@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --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 \
    /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