linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ge Yang <yangge1116@126.com>
To: David Hildenbrand <david@redhat.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, 21cnbao@gmail.com,
	baolin.wang@linux.alibaba.com, liuzixing@hygon.cn
Subject: Re: [PATCH V2] mm/gup: Clear the LRU flag of a page before adding to LRU batch
Date: Tue, 30 Jul 2024 08:57:52 +0800	[thread overview]
Message-ID: <79234eac-d7cc-424b-984d-b78861a5e862@126.com> (raw)
In-Reply-To: <3a2ab0ea-3a07-45a0-ae0e-b9d48bf409bd@redhat.com>



在 2024/7/29 22:04, David Hildenbrand 写道:
> On 22.06.24 08:48, yangge1116@126.com wrote:
>> From: yangge <yangge1116@126.com>
>>
>> If a large number of CMA memory are configured in system (for example, 
>> the
>> CMA memory accounts for 50% of the system memory), starting a virtual
>> virtual machine, it will call pin_user_pages_remote(..., FOLL_LONGTERM,
>> ...) to pin memory.  Normally if a page is present and in CMA area,
>> pin_user_pages_remote() will migrate the page from CMA area to non-CMA
>> area because of FOLL_LONGTERM flag. But the current code will cause the
>> migration failure due to unexpected page refcounts, and eventually cause
>> the virtual machine fail to start.
>>
>> If a page is added in LRU batch, its refcount increases one, remove the
>> page from LRU batch decreases one. Page migration requires the page is 
>> not
>> referenced by others except page mapping. Before migrating a page, we
>> should try to drain the page from LRU batch in case the page is in it,
>> however, folio_test_lru() is not sufficient to tell whether the page is
>> in LRU batch or not, if the page is in LRU batch, the migration will 
>> fail.
>>
>> To solve the problem above, we modify the logic of adding to LRU batch.
>> Before adding a page to LRU batch, we clear the LRU flag of the page so
>> that we can check whether the page is in LRU batch by 
>> folio_test_lru(page).
>> Seems making the LRU flag of the page invisible a long time is no 
>> problem,
>> because a new page is allocated from buddy and added to the lru batch,
>> its LRU flag is also not visible for a long time.
>>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: yangge <yangge1116@126.com>
>> ---
>>   mm/swap.c | 43 +++++++++++++++++++++++++++++++------------
>>   1 file changed, 31 insertions(+), 12 deletions(-)
>>
>> diff --git a/mm/swap.c b/mm/swap.c
>> index dc205bd..9caf6b0 100644
>> --- a/mm/swap.c
>> +++ b/mm/swap.c
>> @@ -211,10 +211,6 @@ static void folio_batch_move_lru(struct 
>> folio_batch *fbatch, move_fn_t move_fn)
>>       for (i = 0; i < folio_batch_count(fbatch); i++) {
>>           struct folio *folio = fbatch->folios[i];
>> -        /* block memcg migration while the folio moves between lru */
>> -        if (move_fn != lru_add_fn && !folio_test_clear_lru(folio))
>> -            continue;
>> -
>>           folio_lruvec_relock_irqsave(folio, &lruvec, &flags);
>>           move_fn(lruvec, folio);
>> @@ -255,11 +251,16 @@ static void lru_move_tail_fn(struct lruvec 
>> *lruvec, struct folio *folio)
>>   void folio_rotate_reclaimable(struct folio *folio)
>>   {
>>       if (!folio_test_locked(folio) && !folio_test_dirty(folio) &&
>> -        !folio_test_unevictable(folio) && folio_test_lru(folio)) {
>> +        !folio_test_unevictable(folio)) {
>>           struct folio_batch *fbatch;
>>           unsigned long flags;
>>           folio_get(folio);
>> +        if (!folio_test_clear_lru(folio)) {
>> +            folio_put(folio);
>> +            return;
>> +        }
>> +
>>           local_lock_irqsave(&lru_rotate.lock, flags);
>>           fbatch = this_cpu_ptr(&lru_rotate.fbatch);
>>           folio_batch_add_and_move(fbatch, folio, lru_move_tail_fn);
>> @@ -352,11 +353,15 @@ static void folio_activate_drain(int cpu)
>>   void folio_activate(struct folio *folio)
>>   {
>> -    if (folio_test_lru(folio) && !folio_test_active(folio) &&
>> -        !folio_test_unevictable(folio)) {
>> +    if (!folio_test_active(folio) && !folio_test_unevictable(folio)) {
>>           struct folio_batch *fbatch;
>>           folio_get(folio);
>> +        if (!folio_test_clear_lru(folio)) {
>> +            folio_put(folio);
>> +            return;
>> +        }
>> +
>>           local_lock(&cpu_fbatches.lock);
>>           fbatch = this_cpu_ptr(&cpu_fbatches.activate);
>>           folio_batch_add_and_move(fbatch, folio, folio_activate_fn);
>> @@ -700,6 +705,11 @@ void deactivate_file_folio(struct folio *folio)
>>           return;
>>       folio_get(folio);
>> +    if (!folio_test_clear_lru(folio)) {
>> +        folio_put(folio);
>> +        return;
>> +    }
>> +
>>       local_lock(&cpu_fbatches.lock);
>>       fbatch = this_cpu_ptr(&cpu_fbatches.lru_deactivate_file);
>>       folio_batch_add_and_move(fbatch, folio, lru_deactivate_file_fn);
>> @@ -716,11 +726,16 @@ void deactivate_file_folio(struct folio *folio)
>>    */
>>   void folio_deactivate(struct folio *folio)
>>   {
>> -    if (folio_test_lru(folio) && !folio_test_unevictable(folio) &&
>> -        (folio_test_active(folio) || lru_gen_enabled())) {
>> +    if (!folio_test_unevictable(folio) && (folio_test_active(folio) ||
>> +        lru_gen_enabled())) {
>>           struct folio_batch *fbatch;
>>           folio_get(folio);
>> +        if (!folio_test_clear_lru(folio)) {
>> +            folio_put(folio);
>> +            return;
>> +        }
>> +
>>           local_lock(&cpu_fbatches.lock);
>>           fbatch = this_cpu_ptr(&cpu_fbatches.lru_deactivate);
>>           folio_batch_add_and_move(fbatch, folio, lru_deactivate_fn);
>> @@ -737,12 +752,16 @@ void folio_deactivate(struct folio *folio)
>>    */
>>   void folio_mark_lazyfree(struct folio *folio)
>>   {
>> -    if (folio_test_lru(folio) && folio_test_anon(folio) &&
>> -        folio_test_swapbacked(folio) && !folio_test_swapcache(folio) &&
>> -        !folio_test_unevictable(folio)) {
>> +    if (folio_test_anon(folio) && folio_test_swapbacked(folio) &&
>> +        !folio_test_swapcache(folio) && 
>> !folio_test_unevictable(folio)) {
>>           struct folio_batch *fbatch;
>>           folio_get(folio);
>> +        if (!folio_test_clear_lru(folio)) {
>> +            folio_put(folio);
>> +            return;
>> +        }
> 
> Looking at this in more detail, I wonder if we can turn that to
> 
> if (!folio_test_clear_lru(folio))
>      return;
> folio_get(folio);
> 
> In all cases? The caller must hold a reference, so this should be fine.
> 

Seems the caller madvise_free_pte_range(...), calling 
folio_mark_lazyfree(...), doesn't hold a reference on folio.



  reply	other threads:[~2024-07-30  0:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-22  6:48 yangge1116
2024-07-03  9:46 ` Barry Song
2024-07-03 11:15   ` Ge Yang
2024-07-03 12:02 ` David Hildenbrand
2024-07-04  6:24   ` Ge Yang
2024-07-27 22:33 ` Chris Li
2024-07-29  0:34   ` Ge Yang
2024-07-29  3:49   ` Ge Yang
2024-07-29 22:06     ` Chris Li
2024-08-02  1:51       ` Ge Yang
2024-08-02 20:18         ` Chris Li
2024-08-03  8:25           ` Ge Yang
2024-08-03 17:08             ` Yu Zhao
2024-08-03 20:03               ` Kairui Song
2024-08-04 12:21                 ` Kairui Song
2024-08-04 17:51                   ` Chris Li
2024-08-04 19:11                     ` Chris Li
2024-09-02 12:53                       ` Linux regression tracking (Thorsten Leemhuis)
2024-09-05  5:00                         ` Chris Li
2024-07-29 14:04 ` David Hildenbrand
2024-07-30  0:57   ` Ge Yang [this message]
2024-07-30  7:45     ` David Hildenbrand
2024-07-30  9:36       ` Ge Yang
2024-07-30  9:41         ` David Hildenbrand
2024-07-30  9:56           ` Ge Yang
2024-07-30  9:58             ` David Hildenbrand
2024-07-30 10:01               ` Ge Yang
2024-12-26  0:31 Andy amonte

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=79234eac-d7cc-424b-984d-b78861a5e862@126.com \
    --to=yangge1116@126.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuzixing@hygon.cn \
    --cc=stable@vger.kernel.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