All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Punit Agrawal <punit.agrawal@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	steve.capper@arm.com, Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] Documentation/arm64: HugeTLB page implementation
Date: Wed, 10 Oct 2018 18:08:58 +0100	[thread overview]
Message-ID: <20181010170857.GF212880@arrakis.emea.arm.com> (raw)
In-Reply-To: <20181009115049.GA6248@arm.com>

On Tue, Oct 09, 2018 at 12:50:49PM +0100, Will Deacon wrote:
> On Tue, Oct 09, 2018 at 11:02:01AM +0100, Punit Agrawal wrote:
> > Randy Dunlap <rdunlap@infradead.org> writes:
> > 
> > > On 10/8/18 3:03 AM, Punit Agrawal wrote:
> > >> Arm v8 architecture supports multiple page sizes - 4k, 16k and
> > >> 64k. Based on the active page size, the Linux port supports
> > >> corresponding hugepage sizes at PMD and PUD(4k only) levels.
> > >> 
> > >> In addition, the architecture also supports caching larger sized
> > >> ranges (composed of multiple entries) at the PTE and PMD level in the
> > >> TLBs using the contiguous bit. The Linux port makes use of this
> > >> architectural support to enable additional hugepage sizes.
> > >> 
> > >> Describe the two different types of hugepages supported by the arm64
> > >> kernel and the hugepage sizes enabled by each.
> > >> 
> > >> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> > >> Cc: Catalin Marinas <catalin.marinas@arm.com>
> > >> Cc: Will Deacon <will.deacon@arm.com>
> > >> Cc: Jonathan Corbet <corbet@lwn.net>
> > >
> > > Acked-by: Randy Dunlap <rdunlap@infradead.org>
> > 
> > Thanks!
> > 
> > Catalin, Will - I assume you'll pick this up at some point? Or do arm64
> > documentation patches get routed by another tree?
> 
> Acked-by: Will Deacon <will.deacon@arm.com>
> 
> Catalin can pick this up for 4.20.

Done.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Documentation/arm64: HugeTLB page implementation
Date: Wed, 10 Oct 2018 18:08:58 +0100	[thread overview]
Message-ID: <20181010170857.GF212880@arrakis.emea.arm.com> (raw)
In-Reply-To: <20181009115049.GA6248@arm.com>

On Tue, Oct 09, 2018 at 12:50:49PM +0100, Will Deacon wrote:
> On Tue, Oct 09, 2018 at 11:02:01AM +0100, Punit Agrawal wrote:
> > Randy Dunlap <rdunlap@infradead.org> writes:
> > 
> > > On 10/8/18 3:03 AM, Punit Agrawal wrote:
> > >> Arm v8 architecture supports multiple page sizes - 4k, 16k and
> > >> 64k. Based on the active page size, the Linux port supports
> > >> corresponding hugepage sizes at PMD and PUD(4k only) levels.
> > >> 
> > >> In addition, the architecture also supports caching larger sized
> > >> ranges (composed of multiple entries) at the PTE and PMD level in the
> > >> TLBs using the contiguous bit. The Linux port makes use of this
> > >> architectural support to enable additional hugepage sizes.
> > >> 
> > >> Describe the two different types of hugepages supported by the arm64
> > >> kernel and the hugepage sizes enabled by each.
> > >> 
> > >> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> > >> Cc: Catalin Marinas <catalin.marinas@arm.com>
> > >> Cc: Will Deacon <will.deacon@arm.com>
> > >> Cc: Jonathan Corbet <corbet@lwn.net>
> > >
> > > Acked-by: Randy Dunlap <rdunlap@infradead.org>
> > 
> > Thanks!
> > 
> > Catalin, Will - I assume you'll pick this up at some point? Or do arm64
> > documentation patches get routed by another tree?
> 
> Acked-by: Will Deacon <will.deacon@arm.com>
> 
> Catalin can pick this up for 4.20.

Done.

-- 
Catalin

  reply	other threads:[~2018-10-10 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 14:34 [PATCH] Documentation/arm64: HugeTLB page implementation Punit Agrawal
2018-10-05 14:34 ` Punit Agrawal
2018-10-06 16:30 ` Randy Dunlap
2018-10-06 16:30   ` Randy Dunlap
2018-10-08  9:39   ` Punit Agrawal
2018-10-08  9:39     ` Punit Agrawal
2018-10-08 10:03   ` [PATCH v2] " Punit Agrawal
2018-10-08 10:03     ` Punit Agrawal
2018-10-08 19:49     ` Randy Dunlap
2018-10-08 19:49       ` Randy Dunlap
2018-10-09 10:02       ` Punit Agrawal
2018-10-09 10:02         ` Punit Agrawal
2018-10-09 11:50         ` Will Deacon
2018-10-09 11:50           ` Will Deacon
2018-10-10 17:08           ` Catalin Marinas [this message]
2018-10-10 17:08             ` Catalin Marinas

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=20181010170857.GF212880@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=steve.capper@arm.com \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.