linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Peter Xu <peterx@redhat.com>, Yang Shi <shy828301@gmail.com>
Cc: david@redhat.com, kirill.shutemov@linux.intel.com,
	jhubbard@nvidia.com, jgg@nvidia.com, hughd@google.com,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: gup: fix the fast GUP race against THP collapse
Date: Mon, 05 Sep 2022 14:26:09 +0530	[thread overview]
Message-ID: <87fsh6jj2u.fsf@linux.ibm.com> (raw)
In-Reply-To: <YxJot6JbFl0HnXq3@xz-m1.local>

Peter Xu <peterx@redhat.com> writes:

>
> On Fri, Sep 02, 2022 at 10:45:20AM -0700, Yang Shi wrote:
>> > How about another patch to remove the ppc impl too?  Then it can be a two
>> > patches series.
>> 
>> BTW, I don't think we could remove the ppc implementation since it is
>> different from the generic pmdp_collapse_flush(), particularly for the
>> hash part IIUC.
>> 
>> The generic version calls flush_tlb_range() -> hash__flush_tlb_range()
>> for hash, but the hash call is actually no-op. The ppc version calls
>> hash__pmdp_collapse_flush() -> flush_tlb_pmd_range(), which does
>> something useful.
>
> One thing I found interesting (and also a bit confused..) is that the ppc
> code used the name flush_tlb_pmd_range() to "flush tlb range in pte level",
> which is kind of against the tlb API design..
>
> The generic tlb API has a very close function called flush_pmd_tlb_range()
> which is only used to do pmd-level flushing, while here the ppc version of
> flush_tlb_pmd_range() is actually flush_tlb_range() in the generic API.
>
> Agreed that it may worth having a look from ppc developers.
>

It is actually flushing the hash page table entries. I will rename
flush_tlb_pmd_range to flush_hash_table_pmd_range().

-aneesh


  reply	other threads:[~2022-09-05  8:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 22:27 [PATCH] mm: gup: fix the fast GUP race against THP collapse Yang Shi
2022-09-01 23:26 ` Peter Xu
2022-09-01 23:50   ` Yang Shi
2022-09-02  6:39     ` David Hildenbrand
2022-09-02 15:23       ` Yang Shi
2022-09-02 15:59     ` Peter Xu
2022-09-02 16:04       ` Peter Xu
2022-09-02 17:30       ` Yang Shi
2022-09-02 17:45       ` Yang Shi
2022-09-02 20:33         ` Peter Xu
2022-09-05  8:56           ` Aneesh Kumar K.V [this message]
2022-09-05  8:54         ` Aneesh Kumar K.V
2022-09-06 19:07           ` Yang Shi
2022-09-07  4:50             ` Aneesh Kumar K V
2022-09-07 17:08               ` Yang Shi
2022-09-04 22:21       ` John Hubbard
2022-09-02  6:42 ` David Hildenbrand
2022-09-04 22:29 ` John Hubbard
2022-09-05  7:59   ` David Hildenbrand
2022-09-05 10:16     ` Baolin Wang
2022-09-05 10:24       ` David Hildenbrand
2022-09-05 11:11         ` David Hildenbrand
2022-09-05 14:35           ` Baolin Wang
2022-09-05 14:40             ` David Hildenbrand
2022-09-06  5:53               ` Baolin Wang
2022-09-06  2:12     ` John Hubbard
2022-09-06 12:50       ` David Hildenbrand
2022-09-06 13:47     ` Jason Gunthorpe
2022-09-06 13:57       ` David Hildenbrand
2022-09-06 14:30         ` Jason Gunthorpe
2022-09-06 14:44           ` David Hildenbrand
2022-09-06 15:33             ` Jason Gunthorpe
2022-09-06 19:11             ` Yang Shi
2022-09-06 23:16             ` John Hubbard
2022-09-06 19:01     ` Yang Shi
2022-09-05  9:03   ` Baolin Wang
2022-09-06 18:50   ` Yang Shi
2022-09-06 21:27     ` John Hubbard

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=87fsh6jj2u.fsf@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=shy828301@gmail.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).