From: Dave Hansen <dave.hansen@intel.com>
To: Masanari Iida <standby24x7@gmail.com>,
corbet@lwn.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lcapitulino@redhat.com
Subject: Re: [PATCH] Documentation: vm: Add 1GB large page support information
Date: Mon, 03 Nov 2014 10:18:18 -0800 [thread overview]
Message-ID: <5457C6EA.3080809@intel.com> (raw)
In-Reply-To: <1414771317-5721-1-git-send-email-standby24x7@gmail.com>
On 10/31/2014 09:01 AM, Masanari Iida wrote:
> --- a/Documentation/vm/hugetlbpage.txt
> +++ b/Documentation/vm/hugetlbpage.txt
> @@ -2,7 +2,8 @@
> The intent of this file is to give a brief summary of hugetlbpage support in
> the Linux kernel. This support is built on top of multiple page size support
> that is provided by most modern architectures. For example, i386
> -architecture supports 4K and 4M (2M in PAE mode) page sizes, ia64
> +architecture supports 4K and 4M (2M in PAE mode) page sizes, x86_64
> +architecture supports 4K, 2M and 1G (SandyBridge or later) page sizes. ia64
> architecture supports multiple page sizes 4K, 8K, 64K, 256K, 1M, 4M, 16M,
> 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
> translations. Typically this is a very scarce resource on processor.
I wouldn't mention SandyBridge. Not all x86 CPUs are Intel. :)
Also, what of the Intel CPUs like the Xeon Phi or the Atom cores? I
have an IvyBridge (>= Sandybridge) mobile CPU in this laptop which does
not support 1G pages.
I would axe the i386-specific reference and just say something generic like:
For example, x86 CPUs normally support 4K and 2M (1G sometimes).
--
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:[~2014-11-03 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:01 Masanari Iida
2014-11-03 14:24 ` Luiz Capitulino
2014-11-03 18:18 ` Dave Hansen [this message]
2014-11-05 15:21 ` Masanari Iida
2014-11-05 15:31 ` Dave Hansen
2014-11-05 22:58 ` Andi Kleen
2014-11-05 23:07 ` Dave Hansen
2014-11-06 15:31 ` [PATCH/v2] " Masanari Iida
2014-11-06 16:40 ` Luiz Capitulino
2014-11-06 20:15 ` Jonathan Corbet
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=5457C6EA.3080809@intel.com \
--to=dave.hansen@intel.com \
--cc=corbet@lwn.net \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=standby24x7@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