From: John Hubbard <jhubbard@nvidia.com>
To: Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>
Cc: Jane Chu <jane.chu@oracle.com>, <linux-mm@kvack.org>
Subject: Re: Splitting pinned folios
Date: Wed, 13 Mar 2024 15:25:54 -0700 [thread overview]
Message-ID: <76ba9c50-6afd-4bd6-8f71-184c524d12da@nvidia.com> (raw)
In-Reply-To: <ZfHF4yNXPQhWz6Q5@casper.infradead.org>
On 3/13/24 08:27, Matthew Wilcox wrote:
> On Wed, Mar 13, 2024 at 10:20:46AM +0100, David Hildenbrand wrote:
>> On 13.03.24 04:16, Matthew Wilcox wrote:
>>> On Tue, Mar 12, 2024 at 06:23:43PM -0700, Jane Chu wrote:
>>>> I noticed this recently
>>>
>>> OK, this is entirely different, so I'm going to start a new thread ;-)
>>>
>>>> * GUP pin and PG_locked transferred to @page. Rest subpages can be freed if
>>>> * they are not mapped.
>>>> *
>>>> * Returns 0 if the hugepage is split successfully.
>>>> * Returns -EBUSY if the page is pinned or if anon_vma disappeared from under
>>>> * us.
>>>> */
>>>> int split_huge_page_to_list(struct page *page, struct list_head *list)
>>>> {
>>>>
>>>> I have a test case with poisoned shmem THP page that was mlocked and
>>>>
>>>> GUP pinned (FOLL_LONGTERM|FOLL_WRITE), but the split succeeded.
>>>
>>> I'm going to blame John for this!
That's a reasonable initial step, yes. haha :)
>>
>> The description is wrong. Whoever calls split_huge_page_to_list() must hold
>> a folio reference.
>>
>> That folio reference will be transferred to @page (not the head page) once
>> split. So @page can be used by the caller after the split succeeded.
>>
Thanks David for responding so quickly with these gup/pup answers. Perhaps I
can fix up that documentation comment a bit.
>>
>>> There's no reference to pincount
>>> anywhere in huge_memory.c, so I have no clue how this comment is even
>>
>> Each pincount increment/decrement must be paired with a folio refcount
>> increment. Therefore, no pincount checks are required.
Yes! In try_grab_folio(), that behavior is documented, although due to
code movement and refactoring, the comment refers to behavior a few lines
above it:
/*
* When pinning a large folio, use an exact count to track it.
*
* However, be sure to *also* increment the normal folio
* refcount field at least once, so that the folio really
* is pinned. That's why the refcount from the earlier
* try_get_folio() is left intact.
*/
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-03-13 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 3:16 Matthew Wilcox
2024-03-13 9:20 ` David Hildenbrand
2024-03-13 15:27 ` Matthew Wilcox
2024-03-13 16:53 ` David Hildenbrand
2024-03-13 18:52 ` Jane Chu
2024-03-13 22:25 ` John Hubbard [this message]
2024-03-14 2:46 ` updated documentation: " John Hubbard
2024-03-14 16:22 ` David Hildenbrand
2024-03-14 17:51 ` John Hubbard
2024-03-14 17:45 ` Matthew Wilcox
2024-03-14 17:57 ` 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=76ba9c50-6afd-4bd6-8f71-184c524d12da@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=david@redhat.com \
--cc=jane.chu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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