linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/vmscan: don't try to reclaim freed folios
Date: Thu, 9 Jun 2022 11:04:02 +0800	[thread overview]
Message-ID: <e7178c73-9dbf-2d5f-735d-c23937fc9997@huawei.com> (raw)
In-Reply-To: <YqDuu2KBofxl1s49@casper.infradead.org>

On 2022/6/9 2:47, Matthew Wilcox wrote:
> On Wed, Jun 08, 2022 at 10:14:32PM +0800, Miaohe Lin wrote:
>> If folios were freed from under us, there's no need to reclaim them. Skip
>> these folios to save lots of cpu cycles and avoid possible unnecessary
>> disk I/O.
> 
> Yes, but I asked how often this happened, and you said you didn't know.
> Do you have any data?  I'm reluctant to make a function which is over

This is just like the page_count == 1 case when doing page migration in unmap_and_move().

> 400 LOC already any longer.

I'm fine to resend this patch until your work is done (It will be really grateful if I
will be notified when that work is done).

Thanks!

> 
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>> v2:
>>   use folio_ref_freeze to guard against race with GUP (fast). Many thanks
>>   Matthew for pointing this out.
>> ---
>>  mm/vmscan.c | 10 ++++++++--
>>  1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 13d34d9593bb..547ae7ae6ab1 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -1610,13 +1610,19 @@ static unsigned int shrink_page_list(struct list_head *page_list,
>>  		folio = lru_to_folio(page_list);
>>  		list_del(&folio->lru);
>>  
>> +		nr_pages = folio_nr_pages(folio);
>> +
>> +		if (folio_ref_count(folio) == 1 &&
>> +		    folio_ref_freeze(folio, 1)) {
>> +			/* folio was freed from under us. So we are done. */
>> +			goto free_it;
>> +		}
>> +
>>  		if (!folio_trylock(folio))
>>  			goto keep;
>>  
>>  		VM_BUG_ON_FOLIO(folio_test_active(folio), folio);
>>  
>> -		nr_pages = folio_nr_pages(folio);
>> -
>>  		/* Account the number of base pages */
>>  		sc->nr_scanned += nr_pages;
>>  
>> -- 
>> 2.23.0
>>
> 
> .
> 



      reply	other threads:[~2022-06-09  3:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 14:14 Miaohe Lin
2022-06-08 18:47 ` Matthew Wilcox
2022-06-09  3:04   ` Miaohe Lin [this message]

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=e7178c73-9dbf-2d5f-735d-c23937fc9997@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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