From: David Hildenbrand <david@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Sasha Levin <sasha.levin@oracle.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Jerome Marchand <jmarchan@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Hugh Dickins <hughd@google.com>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH v1] mm/gup: adjust stale comment for RCU GUP-fast
Date: Thu, 1 Sep 2022 18:30:04 +0200 [thread overview]
Message-ID: <8e566857-d552-86f4-cbbb-5eed9de6acca@redhat.com> (raw)
In-Reply-To: <YxDZ86XW3hPcJtPX@nvidia.com>
On 01.09.22 18:12, Jason Gunthorpe wrote:
> On Thu, Sep 01, 2022 at 09:21:19AM +0200, David Hildenbrand wrote:
>> commit 4b471e8898c3 ("mm, thp: remove infrastructure for handling splitting
>> PMDs") didn't remove all details about the THP split requirements for
>> RCU GUP-fast.
>>
>> IPI broeadcasts on THP split are no longer required.
>>
>> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>> Cc: Sasha Levin <sasha.levin@oracle.com>
>> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> Cc: Vlastimil Babka <vbabka@suse.cz>
>> Cc: Jerome Marchand <jmarchan@redhat.com>
>> Cc: Andrea Arcangeli <aarcange@redhat.com>
>> Cc: Hugh Dickins <hughd@google.com>
>> Cc: Jason Gunthorpe <jgg@nvidia.com>
>> Cc: John Hubbard <jhubbard@nvidia.com>
>> Cc: Peter Xu <peterx@redhat.com>
>> Cc: Yang Shi <shy828301@gmail.com>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> mm/gup.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> The comment a bit above seems to need touching to:
>
> * protected from page table pages being freed from under it, and should
> * block any THP splits.
Ah right. Will drop it as well -- thanks!
>
> What is the current situation for THP splits anyhow? Is there are
> comment in the fast pmd code explaining it?
Not aware of a comment, I think it just works naturally by always
re-routing references taken on tail pages to the head page refcount.
Before that, we had "Tail page refcounting", which -- as I understand --
was a mess.
ddc58f27f9eee9117219936f77e90ad5b2e00e96 contains some comments.
>
> But this seems OK too
>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
>
> Jason
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-09-01 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 7:21 [PATCH v1] mm/gup: adjust stale comment for RCU GUP-fast David Hildenbrand
2022-09-01 14:37 ` Kirill A . Shutemov
2022-09-01 16:12 ` Jason Gunthorpe
2022-09-01 16:30 ` David Hildenbrand [this message]
2022-09-01 16:28 ` Peter Xu
2022-09-01 16:34 ` David Hildenbrand
2022-09-01 16:40 ` Peter Xu
2022-09-01 16:46 ` David Hildenbrand
2022-09-01 17:41 ` Peter Xu
2022-09-01 17:44 ` David Hildenbrand
2022-09-01 17:50 ` Yang Shi
2022-09-01 18:07 ` Peter Xu
2022-09-01 18:35 ` Yang Shi
2022-09-02 6:32 ` David Hildenbrand
2022-09-02 13:53 ` Peter Xu
2022-09-02 15:37 ` Yang Shi
2022-09-04 16:52 ` Aneesh Kumar K V
2022-09-05 8:38 ` David Hildenbrand
2022-09-05 8:41 ` Aneesh Kumar K V
2022-09-04 16:49 ` Aneesh Kumar K V
2022-09-05 8:02 ` 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=8e566857-d552-86f4-cbbb-5eed9de6acca@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=jmarchan@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
/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).