From: Matthew Wilcox <willy@infradead.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Will Deacon <will@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
David Hildenbrand <david@redhat.com>, Yu Zhao <yuzhao@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Yin Fengwei <fengwei.yin@intel.com>,
Yang Shi <shy828301@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>, Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/4] mm/mmu_gather: Store and process pages in contig ranges
Date: Fri, 25 Aug 2023 05:09:19 +0100 [thread overview]
Message-ID: <ZOgpb1Qo5B0r+mhJ@casper.infradead.org> (raw)
In-Reply-To: <20230810103332.3062143-5-ryan.roberts@arm.com>
On Thu, Aug 10, 2023 at 11:33:32AM +0100, Ryan Roberts wrote:
> +void folios_put_refs(struct folio_range *folios, int nr)
> +{
> + int i;
> + LIST_HEAD(pages_to_free);
> + struct lruvec *lruvec = NULL;
> + unsigned long flags = 0;
> + unsigned int lock_batch;
> +
> + for (i = 0; i < nr; i++) {
> + struct folio *folio = page_folio(folios[i].start);
> + int refs = folios[i].end - folios[i].start;
> +
> + /*
> + * Make sure the IRQ-safe lock-holding time does not get
> + * excessive with a continuous string of pages from the
> + * same lruvec. The lock is held only if lruvec != NULL.
> + */
> + if (lruvec && ++lock_batch == SWAP_CLUSTER_MAX) {
> + unlock_page_lruvec_irqrestore(lruvec, flags);
> + lruvec = NULL;
> + }
> +
> + if (is_huge_zero_page(&folio->page))
> + continue;
> +
> + if (folio_is_zone_device(folio)) {
> + if (lruvec) {
> + unlock_page_lruvec_irqrestore(lruvec, flags);
> + lruvec = NULL;
> + }
> + if (put_devmap_managed_page(&folio->page))
> + continue;
> + if (folio_put_testzero(folio))
We're only putting one ref for the zone_device folios? Surely
this should be ref_sub_and_test like below?
> + free_zone_device_page(&folio->page);
> + continue;
> + }
> +
> + if (!folio_ref_sub_and_test(folio, refs))
> + continue;
> +
> + if (folio_test_large(folio)) {
> + if (lruvec) {
> + unlock_page_lruvec_irqrestore(lruvec, flags);
> + lruvec = NULL;
> + }
> + __folio_put_large(folio);
> + continue;
> + }
> +
> + if (folio_test_lru(folio)) {
> + struct lruvec *prev_lruvec = lruvec;
> +
> + lruvec = folio_lruvec_relock_irqsave(folio, lruvec,
> + &flags);
> + if (prev_lruvec != lruvec)
> + lock_batch = 0;
> +
> + lruvec_del_folio(lruvec, folio);
> + __folio_clear_lru_flags(folio);
> + }
> +
> + /*
> + * In rare cases, when truncation or holepunching raced with
> + * munlock after VM_LOCKED was cleared, Mlocked may still be
> + * found set here. This does not indicate a problem, unless
> + * "unevictable_pgs_cleared" appears worryingly large.
> + */
> + if (unlikely(folio_test_mlocked(folio))) {
> + __folio_clear_mlocked(folio);
> + zone_stat_sub_folio(folio, NR_MLOCK);
> + count_vm_event(UNEVICTABLE_PGCLEARED);
> + }
You'll be glad to know I've factored out a nice little helper for that.
next prev parent reply other threads:[~2023-08-25 4:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 10:33 [PATCH v1 0/4] Optimize mmap_exit for large folios Ryan Roberts
2023-08-10 10:33 ` [PATCH v1 1/4] mm: Implement folio_remove_rmap_range() Ryan Roberts
2023-08-10 10:33 ` [PATCH v1 2/4] mm/mmu_gather: generalize mmu_gather rmap removal mechanism Ryan Roberts
2023-08-10 10:33 ` [PATCH v1 3/4] mm/mmu_gather: Remove encoded_page infrastructure Ryan Roberts
2023-08-10 17:34 ` Yu Zhao
2023-08-10 18:31 ` Linus Torvalds
2023-08-10 18:54 ` Ryan Roberts
2023-08-10 10:33 ` [PATCH v1 4/4] mm/mmu_gather: Store and process pages in contig ranges Ryan Roberts
2023-08-10 14:44 ` Zi Yan
2023-08-10 14:55 ` Ryan Roberts
2023-08-10 14:59 ` Zi Yan
2023-08-10 15:05 ` Ryan Roberts
2023-12-04 12:26 ` Ryan Roberts
2023-12-04 12:28 ` David Hildenbrand
2023-12-04 12:39 ` Ryan Roberts
2023-12-04 12:43 ` David Hildenbrand
2023-12-04 12:57 ` Ryan Roberts
2023-08-25 4:09 ` Matthew Wilcox [this message]
2023-08-25 7:13 ` David Hildenbrand
2023-08-29 14:02 ` Ryan Roberts
2023-08-29 14:19 ` Matthew Wilcox
2023-08-29 14:24 ` Matthew Wilcox
2023-08-29 15:59 ` 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=ZOgpb1Qo5B0r+mhJ@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=svens@linux.ibm.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).