public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: mpenttil@redhat.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, John Hubbard <jhubbard@nvidia.com>,
	Ralph Campbell <rcampbell@nvidia.com>
Subject: Re: [PATCH v2] mm/migrate_device: Try to handle swapcache pages
Date: Thu, 01 Jun 2023 22:25:35 +1000	[thread overview]
Message-ID: <87wn0npdnc.fsf@nvidia.com> (raw)
In-Reply-To: <87wn0pt13j.fsf@yhuang6-desk2.ccr.corp.intel.com>


"Huang, Ying" <ying.huang@intel.com> writes:

> mpenttil@redhat.com writes:
>
>> From: Mika Penttilä <mpenttil@redhat.com>
>>
>> Migrating file pages and swapcache pages into device memory is not supported.
>> The decision is done based on page_mapping(). For now, swapcache pages are not migrated.
>>
>> Things can however be improved, for swapcache pages. Try to get rid of the swap cache,
>> and if successful, go ahead as with other anonymous pages.
>>
>> Cc: Alistair Popple <apopple@nvidia.com>
>> Cc: John Hubbard <jhubbard@nvidia.com>
>> Cc: Ralph Campbell <rcampbell@nvidia.com>
>> Cc: Huang Ying <ying.huang@intel.com>
>> Signed-off-by: Mika Penttilä <mpenttil@redhat.com>
>> ---
>>
>> v2:
>>   - use folio_test_anon() (Huang, Ying)
>>
>>  
>>  mm/migrate_device.c | 24 ++++++++++++++++++------
>>  1 file changed, 18 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/migrate_device.c b/mm/migrate_device.c
>> index d30c9de60b0d..829bbc526758 100644
>> --- a/mm/migrate_device.c
>> +++ b/mm/migrate_device.c
>> @@ -747,13 +747,25 @@ static void __migrate_device_pages(unsigned long *src_pfns,
>>  
>>  		if (is_device_private_page(newpage) ||
>>  		    is_device_coherent_page(newpage)) {
>> -			/*
>> -			 * For now only support anonymous memory migrating to
>> -			 * device private or coherent memory.
>> -			 */
>> +
>>  			if (mapping) {
>> -				src_pfns[i] &= ~MIGRATE_PFN_MIGRATE;
>> -				continue;
>> +				struct folio *folio;
>> +
>> +				folio = page_folio(page);
>> +
>> +				/*
>> +				 * For now only support anonymous memory migrating to
>> +				 * device private or coherent memory.
>> +				 *
>> +				 * Try to get rid of swap cache if possible.
>
> I think we can delete the following 2 lines of comments.  They add
> nothing except what code says already.

They are also a bit confusing, because a private file-backed mapping is
treated as anonymous so folio_test_anon() won't filter those
out. 

I will test this tomorrow but the change looks good so please add:

Reviewed-by: Alistair Popple <apopple@nvidia.com>

> Otherwise looks good to me.
>
> Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
>
>> +				 * page is here file or swapcache page, could be shmem also
>> +				 * folio_test_anon() filters out file and shmem
>> +				 *
>> +				 */
>> +				if (!folio_test_anon(folio) || !folio_free_swap(folio)) {
>> +					src_pfns[i] &= ~MIGRATE_PFN_MIGRATE;
>> +					continue;
>> +				}
>>  			}
>>  		} else if (is_zone_device_page(newpage)) {
>>  			/*


      reply	other threads:[~2023-06-01 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  4:40 [PATCH v2] mm/migrate_device: Try to handle swapcache pages mpenttil
2023-05-31  7:24 ` Huang, Ying
2023-06-01 12:25   ` Alistair Popple [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=87wn0npdnc.fsf@nvidia.com \
    --to=apopple@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpenttil@redhat.com \
    --cc=rcampbell@nvidia.com \
    --cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox