linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v7 04/16] powerpc/mm: Avoid useless lock with single page fragments
Date: Wed, 28 Nov 2018 11:46:29 +0000 (UTC)	[thread overview]
Message-ID: <3b06c670786936f1fa184dffb815824b10c6e761.1543405086.git.christophe.leroy@c-s.fr> (raw)
In-Reply-To: <cover.1543405086.git.christophe.leroy@c-s.fr>

There is no point in taking the page table lock as pte_frag or
pmd_frag are always NULL when we have only one fragment.

Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
---
 arch/powerpc/mm/pgtable-book3s64.c | 3 +++
 arch/powerpc/mm/pgtable-frag.c     | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/arch/powerpc/mm/pgtable-book3s64.c b/arch/powerpc/mm/pgtable-book3s64.c
index 0c0fd173208a..f3c31f5e1026 100644
--- a/arch/powerpc/mm/pgtable-book3s64.c
+++ b/arch/powerpc/mm/pgtable-book3s64.c
@@ -244,6 +244,9 @@ static pmd_t *get_pmd_from_cache(struct mm_struct *mm)
 {
 	void *pmd_frag, *ret;
 
+	if (PMD_FRAG_NR == 1)
+		return NULL;
+
 	spin_lock(&mm->page_table_lock);
 	ret = mm->context.pmd_frag;
 	if (ret) {
diff --git a/arch/powerpc/mm/pgtable-frag.c b/arch/powerpc/mm/pgtable-frag.c
index d61e7c2a9a79..7544d0d7177d 100644
--- a/arch/powerpc/mm/pgtable-frag.c
+++ b/arch/powerpc/mm/pgtable-frag.c
@@ -34,6 +34,9 @@ static pte_t *get_pte_from_cache(struct mm_struct *mm)
 {
 	void *pte_frag, *ret;
 
+	if (PTE_FRAG_NR == 1)
+		return NULL;
+
 	spin_lock(&mm->page_table_lock);
 	ret = mm->context.pte_frag;
 	if (ret) {
-- 
2.13.3


  parent reply	other threads:[~2018-11-28 11:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 11:46 [PATCH v7 00/16] Implement use of HW assistance on TLB table walk on 8xx Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 01/16] powerpc/book3s32: Remove CONFIG_BOOKE dependent code Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 02/16] powerpc/8xx: Remove PTE_ATOMIC_UPDATES Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 03/16] powerpc/mm: Move pte_fragment_alloc() to a common location Christophe Leroy
2018-11-28 11:46 ` Christophe Leroy [this message]
2018-11-28 11:46 ` [PATCH v7 05/16] powerpc/mm: move platform specific mmu-xxx.h in platform directories Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 06/16] powerpc/mm: Move pgtable_t into platform headers Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 07/16] powerpc/mm: add helpers to get/set mm.context->pte_frag Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 08/16] powerpc/mm: Extend pte_fragment functionality to PPC32 Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 09/16] powerpc/8xx: Move SW perf counters in first 32kb of memory Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 10/16] powerpc/8xx: Temporarily disable 16k pages and hugepages Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 11/16] powerpc/mm: Use hardware assistance in TLB handlers on the 8xx Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 12/16] powerpc/mm: Enable 8M hugepage support with HW assistance " Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 13/16] powerpc/mm: Enable 512k " Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 14/16] powerpc/mm: reintroduce 16K pages with HW assistance on 8xx Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 15/16] powerpc/8xx: don't use r12/SPRN_SPRG_SCRATCH2 in TLB Miss handlers Christophe Leroy
2018-11-28 11:46 ` [PATCH v7 16/16] powerpc/8xx: regroup TLB handler routines Christophe Leroy

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=3b06c670786936f1fa184dffb815824b10c6e761.1543405086.git.christophe.leroy@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).