linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, linux-mm@kvack.org,
	dave.hansen@intel.com, andi@firstfloor.org
Subject: Re: [PATCH/v2] Documentation: vm: Add 1GB large page support information
Date: Thu, 6 Nov 2014 11:40:05 -0500	[thread overview]
Message-ID: <20141106114005.34dcbf6c@redhat.com> (raw)
In-Reply-To: <1415287875-18820-1-git-send-email-standby24x7@gmail.com>

On Fri,  7 Nov 2014 00:31:15 +0900
Masanari Iida <standby24x7@gmail.com> wrote:

> This patch adds 1GB large page support information in
> Documentation/vm/hugetlbpage.txt
> 
> Reference:
> https://lkml.org/lkml/2014/10/31/366
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  Documentation/vm/hugetlbpage.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/vm/hugetlbpage.txt b/Documentation/vm/hugetlbpage.txt
> index b64e0af..f2d3a10 100644
> --- a/Documentation/vm/hugetlbpage.txt
> +++ b/Documentation/vm/hugetlbpage.txt
> @@ -1,8 +1,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
> +that is provided by most modern architectures.  For example, x86 CPUs normally
> +support 4K and 2M (1G if architecturally supported) 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.

Looks good to me:

Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>

--
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:[~2014-11-06 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 16:01 [PATCH] Documentation: vm: Add 1GB large page support information Masanari Iida
2014-11-03 14:24 ` Luiz Capitulino
2014-11-03 18:18 ` Dave Hansen
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 [this message]
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=20141106114005.34dcbf6c@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@intel.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;
as well as URLs for NNTP newsgroup(s).