From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Pedro Falcato" <pfalcato@suse.de>
Cc: "Harry Yoo" <harry@kernel.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
"Ilya Gladyshev" <ilya.gladyshev@linux.dev>,
"Matthew Wilcox" <willy@infradead.org>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: Improve page refcount scalability
Date: Wed, 14 Oct 2026 18:43:42 +0100 [thread overview]
Message-ID: <3c613725-406a-4506-b788-987a337b9771@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=whzkNzkBmCspHYd80D1Z=krDc4SgVC32=pJ5PtEgqSDrw@mail.gmail.com>
On Wed, Oct 14, 2026, at 17:59, Linus Torvalds wrote:
> That actually makes me think I should go back and clear PG_rcu_free on
> unlink - at that point the folio can no longer be read. I used to
> treat unlink differently from truncate/hole punch because of this, but
> that was in my first version where I marked the pages for freeing when
> removing them from the address space. Now that I mark them at read
> time when they are 'hot', unlink() is still going to pointlessly
> rcu-delay their freeing.
I already have it:
https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git/commit/?id=9d731267fdfeceae023449a768884ee8c66f309d
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-10-14 17:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 18:43 Linus Torvalds
2026-10-13 21:03 ` Matthew Wilcox
2026-10-13 21:26 ` Linus Torvalds
2026-10-13 23:20 ` Paul E. McKenney
2026-10-14 10:36 ` Kiryl Shutsemau
2026-10-14 10:46 ` David Hildenbrand (Arm)
2026-10-13 22:43 ` Kiryl Shutsemau
2026-10-13 23:39 ` Linus Torvalds
2026-10-14 11:53 ` Kiryl Shutsemau
2026-10-14 15:28 ` Matthew Wilcox
2026-10-14 0:10 ` Harry Yoo
2026-10-14 1:01 ` Linus Torvalds
2026-10-14 13:59 ` Pedro Falcato
2026-10-14 16:25 ` Linus Torvalds
2026-10-14 16:59 ` Linus Torvalds
2026-10-14 17:15 ` Linus Torvalds
2026-10-14 17:43 ` Kirill A. Shutemov [this message]
2026-10-14 18:24 ` Linus Torvalds
2026-10-15 2:12 ` Jaegeuk Kim
2026-10-16 14:43 ` Kiryl Shutsemau
2026-10-16 15:41 ` Jaegeuk Kim
2026-10-16 14:40 ` Kiryl Shutsemau
2026-10-16 14:47 ` Linus Torvalds
2026-10-19 14:16 ` Kiryl Shutsemau
2026-10-16 15:14 ` David Hildenbrand (Arm)
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=3c613725-406a-4506-b788-987a337b9771@app.fastmail.com \
--to=kirill@shutemov.name \
--cc=david@kernel.org \
--cc=harry@kernel.org \
--cc=ilya.gladyshev@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mcgrof@kernel.org \
--cc=paulmck@kernel.org \
--cc=pfalcato@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®