From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.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>, Jason Gunthorpe <jgg@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH v1] mm/gup: adjust stale comment for RCU GUP-fast
Date: Thu, 1 Sep 2022 19:44:02 +0200 [thread overview]
Message-ID: <c6990d62-a456-b7c5-f128-311ee758c161@redhat.com> (raw)
In-Reply-To: <YxDu51TQTz8lhIPP@xz-m1.local>
>>> It can be dropped later if you want to rework the thp collapse side and
>>> finally remove IPI dependency on fast-gup, but so far it seems to me it's
>>> still needed. Or just drop this patch until that rework happens?
>>
>> The doc as is is obviously stale, why drop this patch?
>>
>> We should see a fix for the THP collapse issue very soon I guess. Most
>> probably this patch will go upstream after that fix.
>
> No objection to have this patch alone as the removal statement is only
> about "thp split". But IMHO this patch alone didn't really help a great
> lot, especially if you plan to have more to come that is very relevant to
> this, so it'll be clearer to put them together. Your call.
I can hold off the resend until the the fix is in place. Then I can add
to the description that we are not aware of remaining IPI dependencies,
and one undocumented case was broken and got fixed without the need for
IPIs.
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-09-01 17:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 7:21 David Hildenbrand
2022-09-01 14:37 ` Kirill A . Shutemov
2022-09-01 16:12 ` Jason Gunthorpe
2022-09-01 16:30 ` David Hildenbrand
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 [this message]
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=c6990d62-a456-b7c5-f128-311ee758c161@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