From: David Hildenbrand <david@redhat.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/6] mm: ksm: use more folio api in ksm_might_need_to_copy()
Date: Mon, 13 Nov 2023 09:32:26 +0100 [thread overview]
Message-ID: <d5fed34e-359d-4a06-85bd-27694bcf6e4d@redhat.com> (raw)
In-Reply-To: <67eedbab-bf15-4bc3-88ce-36fc074393bd@huawei.com>
On 09.11.23 08:09, Kefeng Wang wrote:
>
>
> On 2023/11/8 21:59, Matthew Wilcox wrote:
>> On Wed, Nov 08, 2023 at 09:40:09AM +0800, Kefeng Wang wrote:
>>>
>>>
>>> On 2023/11/7 22:24, Matthew Wilcox wrote:
>>>> On Tue, Nov 07, 2023 at 09:52:11PM +0800, Kefeng Wang wrote:
>>>>> struct page *ksm_might_need_to_copy(struct page *page,
>>>>> - struct vm_area_struct *vma, unsigned long address)
>>>>> + struct vm_area_struct *vma, unsigned long addr)
>>>>> {
>>>>> struct folio *folio = page_folio(page);
>>>>> struct anon_vma *anon_vma = folio_anon_vma(folio);
>>>>> - struct page *new_page;
>>>>> + struct folio *new_folio;
>>>>> - if (PageKsm(page)) {
>>>>> - if (page_stable_node(page) &&
>>>>> + if (folio_test_ksm(folio)) {
>>>>> + if (folio_stable_node(folio) &&
>>>>> !(ksm_run & KSM_RUN_UNMERGE))
>>>>> return page; /* no need to copy it */
>>>>> } else if (!anon_vma) {
>>>>> return page; /* no need to copy it */
>>>>> - } else if (page->index == linear_page_index(vma, address) &&
>>>>> + } else if (page->index == linear_page_index(vma, addr) &&
>>>>
>>>> Hmm. page->index is going away. What should we do here instead?
>>>
>>> Do you mean to replace page->index to folio->index, or kill index from
>>> struct page?
>>
>> I'm asking you what we should do.
>>
>> Tail pages already don't have a valid ->index (or ->mapping).
>> So presumably we can't see a tail page here today. But will we in future?
>
> I think we could replace page->index to page_to_pgoff(page).
What the second part of that code does is check whether a page might
have been a KSM page before swapout.
Once a KSM page is swapped out, we lose the KSM marker. To recover, we
have to check whether the new page logically "fits" into the VMA.
Large folios are never KSM folios, and we only swap in small folios (and
in the future, once we would swap in large folios, they couldn't have
been KSM folios before).
So you could return early in the function if we have a large folio and
make all operations based on the (small) folio.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-11-13 8:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 13:52 [PATCH 0/6] mm: cleanup and use more folio in page fault Kefeng Wang
2023-11-07 13:52 ` [PATCH 1/6] mm: ksm: use more folio api in ksm_might_need_to_copy() Kefeng Wang
2023-11-07 14:24 ` Matthew Wilcox
2023-11-08 1:40 ` Kefeng Wang
2023-11-08 13:59 ` Matthew Wilcox
2023-11-09 7:09 ` Kefeng Wang
2023-11-13 8:32 ` David Hildenbrand [this message]
2023-11-13 9:51 ` Kefeng Wang
2023-11-07 13:52 ` [PATCH 2/6] mm: memory: use a folio in validate_page_before_insert() Kefeng Wang
2023-11-07 18:17 ` Sidhartha Kumar
2023-11-07 13:52 ` [PATCH 3/6] mm: memory: rename page_copy_prealloc() to folio_prealloc() Kefeng Wang
2023-11-07 18:21 ` Sidhartha Kumar
2023-11-07 13:52 ` [PATCH 4/6] mm: memory: use a folio in do_cow_page() Kefeng Wang
2023-11-07 18:27 ` Sidhartha Kumar
2023-11-08 1:41 ` Kefeng Wang
2023-11-07 13:52 ` [PATCH 5/6] mm: memory: use folio_prealloc() in wp_page_copy() Kefeng Wang
2023-11-07 13:52 ` [PATCH 6/6] mm: memory: use folio_prealloc() in do_anonymous_page() Kefeng Wang
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=d5fed34e-359d-4a06-85bd-27694bcf6e4d@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangkefeng.wang@huawei.com \
--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