linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Bang Li" <libang.li@antgroup.com>
To: David Hildenbrand <david@redhat.com>,
	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,
	ryan.roberts@arm.com, ioworker0@gmail.com,
	libang.linux@gmail.com
Subject: Re: [PATCH v3 1/3] mm: Add update_mmu_tlb_range()
Date: Tue, 21 May 2024 23:36:32 +0800	[thread overview]
Message-ID: <e2646fa8-5f34-4114-b3b4-a6f2ea17d811@antgroup.com> (raw)
In-Reply-To: <b356b558-d327-4bbc-9290-4e296877d145@redhat.com>

Hi David,

Thanks for you review!

On 2024/5/21 17:32, David Hildenbrand wrote:
> On 18.05.24 09:49, Bang Li wrote:
>> Added update_mmu_tlb_range(), we can batch update tlb of an
>> address range.
>>
>> Signed-off-by: Bang Li <libang.li@antgroup.com>
>> ---
> 
> The generic variant that is a NOP from patch #2 should go into this 
> patch as well.

Good point. Thanks for pointing this out.

Thanks,
Bang

> 
> Apart from that LGTM
> 


  parent reply	other threads:[~2024-05-21 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18  7:49 [PATCH v3 0/3] Add update_mmu_tlb_range() to simplify code Bang Li
2024-05-18  7:49 ` [PATCH v3 1/3] mm: Add update_mmu_tlb_range() Bang Li
     [not found]   ` <b356b558-d327-4bbc-9290-4e296877d145@redhat.com>
2024-05-21 15:36     ` Bang Li [this message]
2024-05-18  7:49 ` [PATCH v3 2/3] mm: Refactor update_mmu_tlb() Bang Li
2024-05-21  9:36   ` David Hildenbrand
2024-05-21 15:36     ` Bang Li
2024-05-18  7:49 ` [PATCH v3 3/3] mm: Use update_mmu_tlb_range() to simplify code Bang Li
2024-05-20 14:45   ` Lance Yang
2024-05-21  9:37   ` David Hildenbrand

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=e2646fa8-5f34-4114-b3b4-a6f2ea17d811@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