From: "Bang Li" <libang.li@antgroup.com>
To: akpm@linux-foundation.org, chenhuacai@kernel.org,
tsbogend@alpha.franken.de, paul.walmsley@sifive.com,
palmer@dabbelt.com, chris@zankel.net, jcmvbkbc@gmail.com
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<loongarch@lists.linux.dev>, <linux-riscv@lists.infradead.org>,
<david@redhat.com>, <ryan.roberts@arm.com>, <ioworker0@gmail.com>,
<libang.linux@gmail.com>, "Bang Li" <libang.li@antgroup.com>
Subject: [PATCH v2 0/5] Add update_mmu_tlb_range() to simplify code
Date: Mon, 06 May 2024 23:51:15 +0800 [thread overview]
Message-ID: <20240506155120.83105-1-libang.li@antgroup.com> (raw)
This series of commits mainly adds the update_mmu_tlb_range() to
batch update tlb in an address range.
After the commit 19eaf44954df ("mm: thp: support allocation of anonymous
multi-size THP"), We may need to batch update tlb of a certain address
range by calling update_mmu_tlb() in a loop. Using the
update_mmu_tlb_range(), we can simplify the code and possibly reduce the
execution of some unnecessary code in some architectures.
Thanks,
Bang
Changes since v1 [1]:
- Add __HAVE_ARCH_UPDATE_MMU_TLB_RANGE macro (per Lance Yang)
[1] https://lore.kernel.org/linux-mm/20240429103346.59115-1-libang.li@antgroup.com/
Bang Li (5):
LoongArch: Add update_mmu_tlb_range()
mips: Add update_mmu_tlb_range()
riscv: Add update_mmu_tlb_range()
xtensa: Add update_mmu_tlb_range()
mm: Add update_mmu_tlb_range()
arch/loongarch/include/asm/pgtable.h | 4 ++++
arch/mips/include/asm/pgtable.h | 4 ++++
arch/riscv/include/asm/pgtable.h | 4 ++++
arch/xtensa/include/asm/pgtable.h | 4 ++++
arch/xtensa/mm/tlb.c | 6 ++++++
include/linux/pgtable.h | 8 ++++++++
mm/memory.c | 4 +---
7 files changed, 31 insertions(+), 3 deletions(-)
--
2.19.1.6.gb485710b
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: "Bang Li" <libang.li@antgroup.com>
To: akpm@linux-foundation.org, chenhuacai@kernel.org,
tsbogend@alpha.franken.de, paul.walmsley@sifive.com,
palmer@dabbelt.com, chris@zankel.net, jcmvbkbc@gmail.com
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<loongarch@lists.linux.dev>, <linux-riscv@lists.infradead.org>,
<david@redhat.com>, <ryan.roberts@arm.com>, <ioworker0@gmail.com>,
<libang.linux@gmail.com>, "Bang Li" <libang.li@antgroup.com>
Subject: [PATCH v2 0/5] Add update_mmu_tlb_range() to simplify code
Date: Mon, 06 May 2024 23:51:15 +0800 [thread overview]
Message-ID: <20240506155120.83105-1-libang.li@antgroup.com> (raw)
This series of commits mainly adds the update_mmu_tlb_range() to
batch update tlb in an address range.
After the commit 19eaf44954df ("mm: thp: support allocation of anonymous
multi-size THP"), We may need to batch update tlb of a certain address
range by calling update_mmu_tlb() in a loop. Using the
update_mmu_tlb_range(), we can simplify the code and possibly reduce the
execution of some unnecessary code in some architectures.
Thanks,
Bang
Changes since v1 [1]:
- Add __HAVE_ARCH_UPDATE_MMU_TLB_RANGE macro (per Lance Yang)
[1] https://lore.kernel.org/linux-mm/20240429103346.59115-1-libang.li@antgroup.com/
Bang Li (5):
LoongArch: Add update_mmu_tlb_range()
mips: Add update_mmu_tlb_range()
riscv: Add update_mmu_tlb_range()
xtensa: Add update_mmu_tlb_range()
mm: Add update_mmu_tlb_range()
arch/loongarch/include/asm/pgtable.h | 4 ++++
arch/mips/include/asm/pgtable.h | 4 ++++
arch/riscv/include/asm/pgtable.h | 4 ++++
arch/xtensa/include/asm/pgtable.h | 4 ++++
arch/xtensa/mm/tlb.c | 6 ++++++
include/linux/pgtable.h | 8 ++++++++
mm/memory.c | 4 +---
7 files changed, 31 insertions(+), 3 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2024-05-06 15:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 15:51 Bang Li [this message]
2024-05-06 15:51 ` [PATCH v2 0/5] Add update_mmu_tlb_range() to simplify code Bang Li
2024-05-06 15:51 ` [PATCH v2 1/5] LoongArch: Add update_mmu_tlb_range() Bang Li
2024-05-06 15:51 ` Bang Li
2024-05-06 15:51 ` [PATCH v2 2/5] mips: " Bang Li
2024-05-06 15:51 ` Bang Li
2024-05-06 15:51 ` [PATCH v2 3/5] riscv: " Bang Li
2024-05-06 15:51 ` Bang Li
2024-05-07 5:35 ` Alexandre Ghiti
2024-05-07 5:35 ` Alexandre Ghiti
2024-05-10 2:18 ` Bang Li
2024-05-10 2:18 ` Bang Li
2024-05-06 15:51 ` [PATCH v2 4/5] xtensa: " Bang Li
2024-05-06 15:51 ` Bang Li
2024-05-06 15:51 ` [PATCH v2 5/5] mm: " Bang Li
2024-05-06 15:51 ` Bang Li
2024-05-06 16:07 ` Lance Yang
2024-05-06 16:07 ` Lance Yang
2024-05-07 3:26 ` Bang Li
2024-05-07 3:26 ` Bang Li
2024-05-10 9:05 ` Ryan Roberts
2024-05-10 9:05 ` Ryan Roberts
2024-05-10 9:19 ` Lance Yang
2024-05-10 9:19 ` Lance Yang
2024-05-10 16:36 ` Bang Li
2024-05-10 16:36 ` Bang Li
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=20240506155120.83105-1-libang.li@antgroup.com \
--to=libang.li@antgroup.com \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=chris@zankel.net \
--cc=david@redhat.com \
--cc=ioworker0@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=libang.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ryan.roberts@arm.com \
--cc=tsbogend@alpha.franken.de \
/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.