From: Ryan Roberts <ryan.roberts@arm.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yin Fengwei <fengwei.yin@intel.com>,
David Hildenbrand <david@redhat.com>, Yu Zhao <yuzhao@google.com>,
Yang Shi <shy828301@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>, Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v1 2/3] mm: Implement folio_remove_rmap_range()
Date: Mon, 17 Jul 2023 16:49:19 +0100 [thread overview]
Message-ID: <adac1493-da6d-4581-b8b1-e5911b68cdd7@arm.com> (raw)
In-Reply-To: <ZLVZTupQXt7pAqt8@casper.infradead.org>
On 17/07/2023 16:07, Matthew Wilcox wrote:
> On Mon, Jul 17, 2023 at 03:31:09PM +0100, Ryan Roberts wrote:
>> +/*
>> + * folio_remove_rmap_range - take down pte mappings from a range of pages
>> + * belonging to a folio. All pages are accounted as small pages.
>> + * @folio: folio that all pages belong to
>> + * @page: first page in range to remove mapping from
>> + * @nr: number of pages in range to remove mapping from
>> + * @vma: the vm area from which the mapping is removed
>> + *
>> + * The caller needs to hold the pte lock.
>> + */
>
> This could stand a little reworking. How about this?
>
> /**
> * folio_remove_rmap_range - Take down PTE mappings from a range of pages.
> * @folio: Folio containing all pages in range.
> * @page: First page in range to unmap.
> * @nr: Number of pages to unmap.
> * @vma: The VM area containing the range.
> *
> * All pages in the range must belong to the same VMA & folio. They
> * must be mapped with PTEs, not a PMD.
> *
> * Context: Caller holds the pte lock.
> */
LGTM! thanks.
>
>> +void folio_remove_rmap_range(struct folio *folio, struct page *page,
>> + int nr, struct vm_area_struct *vma)
>> +{
>> + atomic_t *mapped = &folio->_nr_pages_mapped;
>> + int nr_unmapped = 0;
>> + int nr_mapped;
>> + bool last;
>> + enum node_stat_item idx;
>> +
>> + if (unlikely(folio_test_hugetlb(folio))) {
>> + VM_WARN_ON_FOLIO(1, folio);
>> + return;
>> + }
>> +
>> + if (!folio_test_large(folio)) {
>> + /* Is this the page's last map to be removed? */
>> + last = atomic_add_negative(-1, &page->_mapcount);
>> + nr_unmapped = last;
>> + } else {
>> + for (; nr != 0; nr--, page++) {
>> + /* Is this the page's last map to be removed? */
>> + last = atomic_add_negative(-1, &page->_mapcount);
>> + if (last) {
>> + /* Page still mapped if folio mapped entirely */
>> + nr_mapped = atomic_dec_return_relaxed(mapped);
>
> We're still doing one atomic op per page on the folio's nr_pages_mapped
> ... is it possible to batch this and use atomic_sub_return_relaxed()?
Good spot, something like this:
} else {
for (; nr != 0; nr--, page++) {
/* Is this the page's last map to be removed? */
last = atomic_add_negative(-1, &page->_mapcount);
if (last)
nr_unmapped++;
}
/* Pages still mapped if folio mapped entirely */
nr_mapped = atomic_sub_return_relaxed(nr_unmapped, mapped);
if (nr_mapped >= COMPOUND_MAPPED)
nr_unmapped = 0;
}
next prev parent reply other threads:[~2023-07-17 15:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 14:31 [PATCH v1 0/3] Optimize large folio interaction with deferred split Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 1/3] mm: Allow deferred splitting of arbitrary large anon folios Ryan Roberts
2023-07-17 15:30 ` Matthew Wilcox
2023-07-17 15:41 ` Ryan Roberts
2023-07-17 15:43 ` David Hildenbrand
2023-07-17 15:54 ` Matthew Wilcox
2023-07-17 16:17 ` Matthew Wilcox
2023-07-17 16:55 ` David Hildenbrand
2023-07-17 15:42 ` David Hildenbrand
2023-07-17 16:01 ` Ryan Roberts
2023-07-17 16:48 ` David Hildenbrand
2023-07-18 8:58 ` Ryan Roberts
2023-07-18 9:08 ` David Hildenbrand
2023-07-18 9:33 ` Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 2/3] mm: Implement folio_remove_rmap_range() Ryan Roberts
2023-07-17 15:07 ` Matthew Wilcox
2023-07-17 15:49 ` Ryan Roberts [this message]
2023-07-17 15:56 ` Matthew Wilcox
2023-07-17 15:09 ` Zi Yan
2023-07-17 15:51 ` Ryan Roberts
2023-07-17 15:53 ` Zi Yan
2023-07-18 1:14 ` Yin Fengwei
2023-07-18 6:22 ` Huang, Ying
2023-07-18 9:51 ` Ryan Roberts
2023-07-18 7:12 ` Huang, Ying
2023-07-18 10:02 ` Ryan Roberts
2023-07-17 14:31 ` [PATCH v1 3/3] mm: Batch-zap large anonymous folio PTE mappings Ryan Roberts
2023-07-17 15:25 ` Zi Yan
2023-07-17 15:55 ` Ryan Roberts
2023-07-17 16:15 ` Zi Yan
2023-07-18 10:19 ` Ryan Roberts
2023-07-18 14:01 ` Zi Yan
2023-07-17 23:27 ` Yin Fengwei
2023-07-18 10:27 ` Ryan Roberts
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=adac1493-da6d-4581-b8b1-e5911b68cdd7@arm.com \
--to=ryan.roberts@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=yuzhao@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®