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 v4 0/3] Add update_mmu_tlb_range() to simplify code
Date: Wed, 22 May 2024 14:12:01 +0800 [thread overview]
Message-ID: <20240522061204.117421-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 and implement update_mmu_tlb()
using update_mmu_tlb_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 v3 [3]:
- Add acked-by from David Hildenbrand (patch #2 and patch #3) - thanks!
- Add reviewed-by from Lance Yang (patch #3) - thanks!
- Move the general architecture update_mmu_tlb_range() from patch #2 to
patch #1 (per David)
- Update patch #2 commit log (per David)
Changes since v2 [2]:
- Use generic architecture to implement update_mmu_tlb() (per Ryan)
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/
[2] https://lore.kernel.org/linux-mm/20240506155120.83105-1-libang.li@antgroup.com/
[3] https://lore.kernel.org/linux-mm/20240518074914.52170-1-libang.li@antgroup.com/
Bang Li (3):
mm: Add update_mmu_tlb_range()
mm: implement update_mmu_tlb() using update_mmu_tlb_range()
mm: Use update_mmu_tlb_range() to simplify code
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 | 6 +++---
arch/xtensa/mm/tlb.c | 6 +++---
include/linux/pgtable.h | 11 ++++++++---
mm/memory.c | 4 +---
7 files changed, 21 insertions(+), 18 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2024-05-22 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 6:12 Bang Li [this message]
2024-05-22 6:12 ` [PATCH v4 1/3] mm: Add update_mmu_tlb_range() Bang Li
2024-05-22 6:12 ` [PATCH v4 2/3] mm: implement update_mmu_tlb() using update_mmu_tlb_range() Bang Li
2024-05-22 6:12 ` [PATCH v4 3/3] mm: Use update_mmu_tlb_range() to simplify code 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=20240522061204.117421-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox