linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel test robot <yujie.liu@intel.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Hugh Dickins <hughd@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] mm,unmap: avoid flushing TLB in batch if PTE is inaccessible
Date: Wed, 19 Apr 2023 22:58:17 +0000	[thread overview]
Message-ID: <A7009B2B-8480-4AEB-8924-7E520A95386A@vmware.com> (raw)
In-Reply-To: <87a5z5vpy7.fsf@yhuang6-desk2.ccr.corp.intel.com>



> On Apr 17, 2023, at 8:17 PM, Huang, Ying <ying.huang@intel.com> wrote:
> 
> !! External Email
> 
> Nadav Amit <namit@vmware.com> writes:
>> 
>> You didn’t miss anything. I went over the comment on
>> inc_tlb_flush_pending() and you follow the scheme.
> 
> Thanks!  Can I get your acked-by or reviewed-by for this patch?

Reviewed-by: Nadav Amit <namit@vmware.com>

Thanks,
Nadav

  reply	other threads:[~2023-04-19 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  7:52 [PATCH] mm,unmap: avoid flushing TLB in batch if PTE is inaccessible Huang Ying
2023-04-10 19:47 ` Nadav Amit
2023-04-11  1:31   ` Huang, Ying
2023-04-11 17:52     ` Nadav Amit
2023-04-12  1:50       ` Huang, Ying
2023-04-12 17:00         ` Nadav Amit
2023-04-18  3:17           ` Huang, Ying
2023-04-19 22:58             ` Nadav Amit [this message]
2023-04-20  7:44 ` haoxin
2023-04-20  8:38   ` Huang, Ying

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=A7009B2B-8480-4AEB-8924-7E520A95386A@vmware.com \
    --to=namit@vmware.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=yujie.liu@intel.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).