From: Dev Jain <dev.jain@arm.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, david@redhat.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, baohua@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] khugepaged: Reduce race probability between migration and khugepaged
Date: Thu, 26 Jun 2025 10:34:45 +0530 [thread overview]
Message-ID: <b5bf26a4-e276-4b26-bf1a-d5af53529e2f@arm.com> (raw)
In-Reply-To: <f3b2ae95-cc0e-42a5-858e-a614578553a6@lucifer.local>
On 26/06/25 10:32 am, Lorenzo Stoakes wrote:
> On Thu, Jun 26, 2025 at 10:29:22AM +0530, Dev Jain wrote:
>> On 26/06/25 10:27 am, Lorenzo Stoakes wrote:
>>> On Thu, Jun 26, 2025 at 09:22:28AM +0530, Dev Jain wrote:
>>>> On 25/06/25 6:58 pm, Lorenzo Stoakes wrote:
>>>>> On Wed, Jun 25, 2025 at 11:28:06AM +0530, Dev Jain wrote:
>>>>>> Suppose a folio is under migration, and khugepaged is also trying to
>>>>>> collapse it. collapse_pte_mapped_thp() will retrieve the folio from the
>>>>>> page cache via filemap_lock_folio(), thus taking a reference on the folio
>>>>>> and sleeping on the folio lock, since the lock is held by the migration
>>>>>> path. Migration will then fail in
>>>>>> __folio_migrate_mapping -> folio_ref_freeze. Reduce the probability of
>>>>>> such a race happening (leading to migration failure) by bailing out
>>>>>> if we detect a PMD is marked with a migration entry.
>>>>>>
>>>>>> This fixes the migration-shared-anon-thp testcase failure on Apple M3.
>>>>> Hm is this related to the series at all? Seems somewhat unrelated?
>>>> Not related.
>>>>
>>>>> Is there a Fixes, Closes, etc.? Do we need something in stable?
>>>> We don't need anything. This is an "expected race" in the sense that
>>>> both migration and khugepaged collapse are best effort algorithms.
>>>> I am just seeing a test failure on my system because my system hits
>>>> the race more often. So this patch reduces the window for the race.
>>> Does it rely on previous patches? If not probably best to send this one
>>> separately :)
>> To prevent rebasing headaches for others (if any) I thought to send all together.
>> I'll send it separately if still that is the preference.
>>
>>
> Oh actually would it be a pain to rebase given the previous 2 patches? Maybe
Didn't take the time to actually check that, more of a "it *may* be a pain
so let's send this together".
> leave it then. And I can actually finally review it... :)
next prev parent reply other threads:[~2025-06-26 5:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 5:58 [PATCH v2 0/3] Optimizations for khugepaged Dev Jain
2025-06-25 5:58 ` [PATCH 1/3] khugepaged: Optimize __collapse_huge_page_copy_succeeded() by PTE batching Dev Jain
2025-06-25 11:14 ` David Hildenbrand
2025-06-25 11:19 ` Dev Jain
2025-06-25 12:14 ` Lorenzo Stoakes
2025-06-25 12:22 ` David Hildenbrand
2025-06-26 3:53 ` Dev Jain
2025-06-25 5:58 ` [PATCH v2 2/3] khugepaged: Optimize collapse_pte_mapped_thp() for large folios " Dev Jain
2025-06-25 13:11 ` Lorenzo Stoakes
2025-06-26 3:48 ` Dev Jain
2025-06-26 4:47 ` Lorenzo Stoakes
2025-06-26 4:54 ` Dev Jain
2025-07-15 6:34 ` Dev Jain
2025-07-15 9:43 ` Lorenzo Stoakes
2025-07-15 9:56 ` David Hildenbrand
2025-07-15 10:02 ` Lorenzo Stoakes
2025-07-15 10:40 ` Dev Jain
2025-07-15 11:13 ` Lorenzo Stoakes
2025-06-25 5:58 ` [PATCH v2 3/3] khugepaged: Reduce race probability between migration and khugepaged Dev Jain
2025-06-25 13:28 ` Lorenzo Stoakes
2025-06-26 3:52 ` Dev Jain
2025-06-26 4:57 ` Lorenzo Stoakes
2025-06-26 4:59 ` Dev Jain
2025-06-26 5:02 ` Lorenzo Stoakes
2025-06-26 5:04 ` Dev Jain [this message]
2025-06-26 5:06 ` Lorenzo Stoakes
2025-06-26 5:27 ` Dev Jain
2025-06-25 10:36 ` [PATCH v2 0/3] Optimizations for khugepaged Lorenzo Stoakes
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=b5bf26a4-e276-4b26-bf1a-d5af53529e2f@arm.com \
--to=dev.jain@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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.