From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: John Hubbard <jhubbard@nvidia.com>,
Yang Shi <shy828301@gmail.com>,
peterx@redhat.com, kirill.shutemov@linux.intel.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: Tue, 6 Sep 2022 12:33:21 -0300 [thread overview]
Message-ID: <YxdoQR30GXfTH/6K@nvidia.com> (raw)
In-Reply-To: <40486dbb-9f19-6fa6-d46d-99d2b033883d@redhat.com>
On Tue, Sep 06, 2022 at 04:44:20PM +0200, David Hildenbrand wrote:
> ... I do wonder if we want to reuse ptep_get_lockless() instead of the
> READ_ONCE(). CONFIG_GUP_GET_PTE_LOW_HIGH is confusing.
Yes, that is a whole other topic, and you may be quite right on that.
Jason
next prev parent reply other threads:[~2022-09-06 15:33 UTC|newest]
Thread overview: 40+ 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
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 4:50 ` Aneesh Kumar K V
2022-09-07 17:08 ` Yang Shi
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 [this message]
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=YxdoQR30GXfTH/6K@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.