From: Barry Song <21cnbao@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: wangkefeng.wang@huawei.com, prime.zeng@hisilicon.com,
linux-doc@vger.kernel.org, peterz@infradead.org,
catalin.marinas@arm.com, yangyicong@hisilicon.com,
linux-mm@kvack.org, guojian@oppo.com,
linux-riscv@lists.infradead.org, will@kernel.org,
linux-s390@vger.kernel.org, zhangshiming@oppo.com,
lipeifeng@oppo.com, corbet@lwn.net, x86@kernel.org,
linux-mips@vger.kernel.org, arnd@arndb.de, realmz6@gmail.com,
Barry Song <v-songbaohua@oppo.com>,
openrisc@lists.librecores.org, darren@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org, xhao@linux.alibaba.com,
linux-kernel@vger.kernel.org, huzhanyuan@oppo.com,
Yicong Yang <yangyicong@huawei.com>,
akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/4] Revert "Documentation/features: mark BATCHED_UNMAP_TLB_FLUSH doesn't apply to ARM64"
Date: Fri, 9 Sep 2022 16:40:11 +1200 [thread overview]
Message-ID: <CAGsJ_4zajhnbt47HQHCyu7fL5Y-b3BOb8MSCb2kr2CfW+gC5gg@mail.gmail.com> (raw)
In-Reply-To: <cc68c8c0-0db1-1678-2095-54383c1383ad@arm.com>
On Fri, Sep 9, 2022 at 4:26 PM Anshuman Khandual
<anshuman.khandual@arm.com> wrote:
>
>
>
> On 8/22/22 13:51, Yicong Yang wrote:
> > From: Barry Song <v-songbaohua@oppo.com>
> >
> > This reverts commit 6bfef171d0d74cb050112e0e49feb20bfddf7f42.
> >
> > I was wrong. Though ARM64 has hardware TLB flush, but it is not free
> > and it is still expensive.
> > We still have a good chance to enable batched and deferred TLB flush
> > on ARM64 for memory reclamation. A possible way is that we only queue
> > tlbi instructions in hardware's queue. When we have to broadcast TLB,
> > we broadcast it by dsb. We just need to get adapted the existing
> > BATCHED_UNMAP_TLB_FLUSH.
> >
> > Tested-by: Xin Hao <xhao@linux.alibaba.com>
> > Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> > Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> > ---
> > Documentation/features/arch-support.txt | 1 -
> > Documentation/features/vm/TLB/arch-support.txt | 2 +-
> > 2 files changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/Documentation/features/arch-support.txt b/Documentation/features/arch-support.txt
> > index 118ae031840b..d22a1095e661 100644
> > --- a/Documentation/features/arch-support.txt
> > +++ b/Documentation/features/arch-support.txt
> > @@ -8,5 +8,4 @@ The meaning of entries in the tables is:
> > | ok | # feature supported by the architecture
> > |TODO| # feature not yet supported by the architecture
> > | .. | # feature cannot be supported by the hardware
> > - | N/A| # feature doesn't apply to the architecture
> >
> > diff --git a/Documentation/features/vm/TLB/arch-support.txt b/Documentation/features/vm/TLB/arch-support.txt
> > index 039e4e91ada3..1c009312b9c1 100644
> > --- a/Documentation/features/vm/TLB/arch-support.txt
> > +++ b/Documentation/features/vm/TLB/arch-support.txt
> > @@ -9,7 +9,7 @@
> > | alpha: | TODO |
> > | arc: | TODO |
> > | arm: | TODO |
> > - | arm64: | N/A |
> > + | arm64: | TODO |
> > | csky: | TODO |
> > | hexagon: | TODO |
> > | ia64: | TODO |
>
> I believe this patch is not needed, which explicitly reverts an
> older commit. Instead when ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
> framework gets enabled on arm64, the same patch could just drop
> 'NA' as possible values for arch support for a give feature in
> file Documentation/features/arch-support.txt.
Sure. it is certainly ok to fix this in
arm64: support batched/deferred tlb shootdown during page reclamation
By a separate patch, I was trying to highlight that my previous patch was
wrong. but, yes. it is not fundamentally necessary.
Thanks
Barry
next prev parent reply other threads:[~2022-09-09 4:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 8:21 [PATCH v3 0/4] mm: arm64: bring up BATCHED_UNMAP_TLB_FLUSH Yicong Yang
2022-08-22 8:21 ` [PATCH v3 1/4] Revert "Documentation/features: mark BATCHED_UNMAP_TLB_FLUSH doesn't apply to ARM64" Yicong Yang
2022-09-09 4:26 ` Anshuman Khandual
2022-09-09 4:40 ` Barry Song [this message]
2022-08-22 8:21 ` [PATCH v3 2/4] mm/tlbbatch: Introduce arch_tlbbatch_should_defer() Yicong Yang
2022-08-24 9:40 ` Kefeng Wang
2022-09-09 4:16 ` Anshuman Khandual
2022-08-22 8:21 ` [PATCH v3 3/4] mm: rmap: Extend tlbbatch APIs to fit new platforms Yicong Yang
2022-08-24 9:43 ` Kefeng Wang
2022-09-09 4:51 ` Anshuman Khandual
2022-09-09 5:25 ` Barry Song
2022-08-22 8:21 ` [PATCH v3 4/4] arm64: support batched/deferred tlb shootdown during page reclamation Yicong Yang
2022-08-24 9:46 ` Kefeng Wang
2022-09-09 5:24 ` Anshuman Khandual
2022-09-09 5:35 ` Barry Song
2022-09-09 6:32 ` Yicong Yang
2022-09-15 6:07 ` Anshuman Khandual
2022-09-15 6:42 ` Barry Song
2022-09-15 14:31 ` Nadav Amit
2022-09-19 2:46 ` Anshuman Khandual
2022-09-19 4:24 ` Anshuman Khandual
2022-09-19 4:53 ` Barry Song
2022-09-19 5:08 ` Barry Song
2022-09-20 3:00 ` Anshuman Khandual
2022-09-20 3:39 ` Barry Song
2022-09-20 8:45 ` Anshuman Khandual
2022-09-21 1:50 ` Barry Song
2022-09-21 1:51 ` Barry Song
2022-09-21 3:33 ` Anshuman Khandual
2022-09-21 6:53 ` Anshuman Khandual
2022-09-21 7:15 ` Barry Song
2022-09-21 7:17 ` Nadav Amit
2022-09-22 3:15 ` Anshuman Khandual
2022-09-06 8:53 ` [PATCH v3 0/4] mm: arm64: bring up BATCHED_UNMAP_TLB_FLUSH Yicong Yang
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=CAGsJ_4zajhnbt47HQHCyu7fL5Y-b3BOb8MSCb2kr2CfW+gC5gg@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=darren@os.amperecomputing.com \
--cc=guojian@oppo.com \
--cc=huzhanyuan@oppo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lipeifeng@oppo.com \
--cc=openrisc@lists.librecores.org \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=realmz6@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xhao@linux.alibaba.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.com \
--cc=zhangshiming@oppo.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).